AI Agent Node
Configure an AI agent that uses tools and integrations to complete a task
The AI Agent node runs an AI model on a task. On each step the agent may call one of its tools, read the result and decide what to do next, until the task is done or the step limit is reached. You find it in the node picker under Agents.
Configuration
| Input | Required | Description |
|---|---|---|
| Model | Yes | The language model. Models differ in capability and price |
| System Prompt | No | Lasting instructions: role, tone, constraints |
| Task | Yes | The job for this run. Reference earlier outputs with {{nodeName.outputs.fieldName}} |
| Attachments | No | Images or PDF files for the agent to analyze, one per line (see below) |
| Tools | No | Skills and integration actions the agent may call |
| Output format | No | Fields the final result must contain (see below) |
| Max. steps | No | Maximum number of iterations, 1 to 50 (default 10) |
Attachments
The agent reads PDF files and images (PNG, JPEG, GIF, WebP). Each line of Attachments is one of:
- a file from an earlier node, for example
{{getEmail.outputs.attachments[0].file}}for the first attachment of an email, or the file from a form upload - all attachments of an email at once:
{{getEmail.outputs.attachments}} - a public URL of an image or PDF
A file from an earlier node of any other type, such as a Word document, makes the node fail with an error that names the file. A file labelled with a generic type is recognised by its name (.pdf, .png, .jpg, .gif, .webp).
Outputs
| Output | Type | Description |
|---|---|---|
result | string or object | The final answer. An object with your fields if an output format is defined, otherwise text |
steps | number | How many steps the agent took |
inputTokens | number | Input tokens across all steps |
outputTokens | number | Output tokens across all steps |
Tools
Click Add tool to give the agent something to call:
- Skills: Web Search searches the internet, Website Scraper extracts the content of web pages (HTML and PDF).
- Integration actions: any action of an integration, such as searching Jira issues or sending a Slack message. Each integration tool needs its own connection.
- MCP servers: the tools of a custom MCP server you have connected. Pick the server, then one or more of its tools. If the picker does not know the server's tools yet, it asks the server; Refresh reloads the list.
The agent decides on its own which tools to use and in which order.
A selected tool counts as approved; nobody is asked during a workflow run. An MCP tool that the person who owns the connection set to Never allow, or an MCP server the organisation switched off for them, makes the node fail. The error message names the reason. A tool whose saved configuration is not valid also makes the node fail, with an error that names the node and the tool; an invalid skill is left out of the run instead, with a warning in the node's output. In both cases, select the tool again in the node.
Only give the agent the tools the task needs. Every extra tool costs tokens and invites unnecessary calls. If an integration action changes data, consider switching on Approval required for the whole node.
Output Format
Without an output format, result is plain text. With one, result is an object that contains exactly the fields you defined, which makes it easy to use in later nodes.
Click Add output field and set for each field:
- Key: the field name, without spaces, for example
summary - Label: a readable name
- Type: Text, Number, Boolean, Selection (with a list of options), Array or Object
- Description: tells the model what belongs in the field
- Required field: whether the field must be filled
A later node then reads a field as {{aiAgent.outputs.result.summary}}.
Tips
Write specific tasks. Instead of "Summarize this", write "Summarize the following support ticket in two or three sentences, name the main issue and suggest a reply. Ticket: {{formTrigger.outputs.formData.ticket}}".
Put lasting instructions in the system prompt. Role, format and tone belong there, so the task stays short.
Lower Max. steps for simple jobs. Classification or extraction without tools needs a single step.
Use an output format for wiring. If the next node needs a particular field, define it. Then it exists and has the right type.