agenthub · document.append
Add a line to one of the business's documents. Safe when several people are talking to the agent at once — every append lands.
Why the node earns its place
The write counterpart to Document Fetch, and together they make a document the agent both reads from and adds to with no re-index in between: fetch reads the markdown source directly, so anything appended is grounding context on the very next turn.
The document is chosen, never created. An agent that could mint documents would quietly fill a business's Document Space with things nobody asked for; picking one from the dropdown keeps the author in charge of what exists.
How it works at run time
{{placeholders}} in the text — dotted paths included, saved variables winning over seeded context keys.What you wire
Configuration
| Key | Type | Default & options | What it does |
|---|---|---|---|
| document_id * | string | choices from distribution:documents | The document to append to, from the Documents tab. Text documents only — spreadsheets and PDFs can't be appended to. |
| text | string | — | What to append. Free-form. Supports {{key}} — e.g. '{{name}} asked about pricing on {{current_date}}'. A wired `text` input wins over this. |
| separator | string | default "newline" newline · blank_line · space · none · custom | What goes between the existing text and the new text. newline starts a new line (the default); blank_line leaves an empty line between entries; custom uses the field below. Never applied to an empty document. |
| custom_separator | string | — | Used only when separator is 'custom', e.g. ' — ' or '\n---\n'. Supports {{key}}. |
What usually goes wrong
Watch for this
Text documents only — spreadsheets and PDFs cannot be appended to, and will not appear in the picker. This node writes outside the run, so a resumed run can append twice; it dedupes on the run-node key rather than assuming it will only ever execute once.
Behaviour & provenance