Agent Connector Setup Guides

Connectors send data from an agent flow to an external automation platform through a webhook. This article explains how to set up the n8n and Zapier connectors, with an example for each. For an introduction to agents, see Agents.
In this article
• Before you start
• n8n Connector
• Zapier Connector
Before you start
• An agent flow exists in the Flow Builder. See Agents.
• The step before the connector produces valid JSON, for example a Prompt action with Output Type set to JSON. See the Agent Actions Reference.
• You have a webhook URL from the external platform: an n8n Webhook node, or a Webhooks by Zapier trigger.

Connector	Execution modes	Trigger in the external platform
n8n	Fire-and-Forget, Synchronous	n8n Webhook node
Zapier	Fire and Forget	Webhooks by Zapier (Catch Hook)

n8n Connector
The n8n Connector allows users to connect their agent flows with external workflows created in n8n. Using this connector, flow can send structured JSON data to an n8n webhook and optionally wait for a response or callback before continuing execution.
The connector is designed for flexible automation scenarios such as:
• Triggering external workflows.
• Sending data to third party systems.
• Processing AI-generated outputs.
• Running background automations.
• Receiving asynchronous updates from external services.
Activity flow
The n8n Connector is an activity available inside the Flow Builder.
It allows your agent flow to:

Send JSON payloads to an n8n webhook URL.
Choose how execution should behave.
Optionally receive a response from n8n.
Continue downstream execution using returned data.
How the connection works
The connector communicates with n8n using a webhook URL.
Flow execution process
Agent Flow
↓
n8n Connector
↓
Webhook Request Sent to n8n
↓
n8n Workflow Executes
↓
(Optional Response or Callback)
↓
Flow Continues

Add the n8n connector
To add the connector:

Open the Flow Builder.
Click Add Activity.
Search for n8n Connector
Select the connector
Configure the required settings
The connector appears in the activity catalog alongside other available integrations.
Connector configuration
Webhook URL
The Webhook URL is the endpoint exposed by your n8n workflow.
Example:
https://your-n8n-instance/webhook/register-user
The connector sends JSON payloads to this endpoint during execution.
Requirements
• Must be a valid HTTPS URL
• Must point to an active n8n webhook
• Must accept JSON requests
Supported execution modes
The connector supports two execution modes.
Each mode controls how the flow waits for and processes responses from n8n.
Fire-and-Forget Mode
The flow sends data to n8n and immediately continues execution without waiting for a response
Best For
• Notifications
• Logging
• Background automation
Synchronous Mode
The flow waits for n8n to finish processing and return a response.
Best For
• Real-time processing.
• Data enrichment
• Validation workflows
Authentication configuration
The connector supports optional authentication settings.
User can configure authentication details required by your n8n webhook.
Supported approaches may include:
• API Key headers.
• JWT tokens.
• Custom authentication headers.
JSON input requirements
The n8n Connector accepts only valid JSON input.
Important
The upstream activity connected to the n8n Connector must produce structured JSON output.
Supported example: {"taskTitle": "Create Report", "assignedTo": "John"}
Unsupported example:
This is plain text
Validation rules
The UI validates configuration before saving or execution.
Validation includes:
• Missing webhook URL
• Invalid URL format
• Unsupported execution mode
• Invalid JSON structure
• Missing required authentication fields
• Contradictory configuration settings
Warnings may also appear if the connector is attached to a non-JSON-producing upstream step.
Timeout and retry settings
Depending on platform configuration, users may configure:
• Request timeout duration
• Retry attempts
These settings help improve reliability for temporary failures or slow external systems.

Figure 1. Agent canvas with the n8n Connector Settings panel open, showing the webhook URL, headers and payload fields.
Example: route by email domain
The following agent is created using the n8n Connector. The agent collects data from HTML fields and checks the email entered in the Notes field to determine whether it belongs to Outlook or Gmail. Based on the email type, a different action is performed.
Agent configuration on the portal
The agent is created with the following actions:

HTML Capture
Captures user input from website fields.
Interaction Type: Answer
Displays the captured field data on the UI.
Prompt
The prompt converts the captured data into JSON format and sends it to n8n through a webhook.
n8n connector
This action type connects with n8n via webhook URL and then run the n8n process.
n8n workflow
The n8n workflow performs the following actions:
• Receives data from the webhook.
• Captures and processes the received fields.
• Sends an email using the captured information.
• Checks conditions based on the email domain.
Conditional actions
• If the email belongs to Outlook:
A folder is created in Google Drive
• If the email belongs to Gmail:
An Excel sheet is created in Google Sheets
Workflow execution
The HTML Capture action collects field data from the website.
The Answer interaction displays the captured data on the UI.
The prompt converts the data into JSON format.
The JSON payload is sent to n8n via webhook.
n8n processes the workflow and evaluates the email condition.
Based on the email type:
o A Google Drive folder is created for Outlook emails, or
o A Google Sheet is created for Gmail emails.

Figure 2. n8n example flow on the canvas: Start, HTML Capture, Answer, Prompt, n8n connector and End.
Zapier Connector
The Zapier Connector allows users to connect their workflows with Zapier automations. It sends structured JSON data from user's flow to a Zapier webhook, enabling integration with thousands of applications and services supported by Zapier.
The connector supports Fire and Forget execution modes : Sends data to Zapier and immediately continues the flow.
When to use the Zapier connector
Use the Zapier Connector when you want to:
• Trigger Zapier workflows from your process.
• Send data to external applications connected through Zapier.
• Automate notifications, CRM updates, ticket creation, document generation and more.
• Receive processed results from Zapier before continuing your workflow.
Prerequisites
• Create a Zapier automation that starts with a Webhook Trigger.
• Copy the webhook URL provided by Zapier.
• Ensure the previous step in your flow produces valid JSON data.
Configuration
Webhook URL
Enter the Zapier webhook URL that will receive data from the flow.
Payload
The connector accepts only valid JSON payloads.
Headers
Users can add custom HTTP headers if required by your integration.
Authentication (Optional)
If Zapier setup requires authentication, user can configure additional authorization headers or credentials as needed.
Timeout and retry settings
Depending on platform configuration, users may configure:
• Request timeout duration
• Retry attempts
These settings help improve reliability for temporary failures or slow external systems.

Figure 3. Zapier Connector Settings showing Node Title, Active, Webhook URL, HTTP Method (POST) and a Payload that references a previous step.

Example: age-based email notification
The following agent is created using the Zapier Connector. The agent collects a user's age, sends the information to Zapier for processing, and triggers different email notifications based on whether the user qualifies as a senior citizen.
Agent flow configuration

Knowly Interaction – Follow-up Question
A Follow up interaction is used to ask the user:
"What is your age?"
The user's response is collected for further processing.
Prompt
A Prompt activity converts the user's response into a valid JSON structure that can be sent to Zapier.
Knowly Interaction – Answer
An Answer interaction displays the captured age on the UI.
Zapier Connector
The Zapier Connector sends the JSON payload to a configured Zapier webhook URL.
The payload uses dynamic data received from the user during the conversation.

Figure 4. Zapier example flow on the canvas: Start, follow-up question, Prompt, Answer, Zapier connector and End.

Zapier workflow configuration

Webhook Trigger
The Zapier workflow starts with a Webhook Trigger that receives the age data sent by the agent.
Conditional Branching
Zapier evaluates the received age and routes the workflow through one of two paths:
Condition 1: Age is less than 50
If the user's age is below 50, Zapier sends an email with the message:
"Your age is less than 50."
Condition 2: Age is 50 or greater
If the user's age is 50 or above, Zapier sends an email with the message:
"You are classified as a senior citizen."
Email Notification
Based on the evaluated condition, Zapier automatically sends the appropriate email to the user.

Figure 5. Zapier Zap: Webhooks by Zapier Catch Raw Hook trigger split into two paths (age under 50 and 50 or over), each ending in a Gmail Send Email step.

If a connector cannot be saved or a call fails, see Agent Troubleshooting and Logs.
Related articles
• Agents
• Agent Actions Reference
• Agent Troubleshooting and Logs
• Version 3.6 release notes