agenthub · input.bigtext
Big Text Input
A named, long-form field the run is started with — a résumé, a job description, a transcript — rather than a chat turn.
Why the node earns its place
Chat Input carries whatever someone typed at an agent. Big Text is for a workflow that is handed a document to work on, where the input is a named slot the caller fills rather than a conversation.
The label you set is what the person or the calling system sees, so name it for the content — Resume, Job Description — not for the node.
How it works at run time
- 1Resolve the value under the same four conventions Chat Input uses, so an SDK caller may address the slot by a stable node name instead of the runtime node id, which changes whenever the agent is rebuilt.
- 2Emit it unchanged on
value.
What you wire
Inputs
Nothing to wire in.
Outputs
- valuestring
Configuration
| Key | Type | Default & options | What it does |
|---|---|---|---|
| label * | string | — | Label shown in UI (e.g. Resume, Job Description) |
| placeholder | string | — | Placeholder text in UI |
| required | boolean | default true | — |
What usually goes wrong
Watch for this
Address the slot by node name from an SDK caller. The node id is regenerated on rebuild, so a payload keyed by id quietly stops matching after a republish and the field arrives empty.
Behaviour & provenance