Connector Modes
Choose how a connector triggers agents, delivers results, or waits for a response.
Connectors are integration points that define how agents are triggered, how they receive input, and where they send results. Each connector can be linked to one or more agents. When triggered, it dispatches the input to all linked agents.
Connect one trigger to multiple agents simultaneously
Inbound, outbound, and sync integration patterns
Built-in authentication and encryption for all connectors
How to Add a Connector
The setup flow is the same for every connector type. Start from the agent you want to connect:
Open your agent
Go to Agents in the sidebar and click on the agent you want to connect.
Add a connector
In the Connector Flow section, click Add inbound connector or Add outbound connector, then click Create New Connector in the drawer that opens.
Choose type and mode
Select a connector type from the marketplace (HTTP Webhook, Kafka, Cron, etc.), then choose a mode and fill in any connector-specific settings.
Create and copy credentials
Click Create. The detail drawer opens automatically with credentials (URL, secret) in the Configuration section. To view them later, hover over the connector in the Connector Flow and click the Eye icon.
The same connector can be linked to multiple agents, so one trigger fans out to all of them. Link or unlink agents later from the connector detail drawer.
Inbound, outbound, and sync
Connectors operate in one of three modes, each designed for different integration patterns:
Fire-and-forget async triggers
Deliver results externally
Request-response pattern
Inbound mode is for fire-and-forget scenarios. When an inbound connector receives a request, it queues the agent run and returns a response with the run ID.
Best for:
- Background processing tasks
- High-volume webhook ingestion
- Event-driven architectures
- When you don't need immediate results
Response:
{"status": "ok", "dispatched_to": 2, "run_ids": ["uuid-1", "uuid-2"]}Outbound mode sends agent results to an external URL when runs complete. Useful for integrating with external systems that need to receive agent outputs.
Best for:
- Sending results to external APIs
- Integrating with third-party services
- Building event pipelines
- Notifying external systems
Outbound Payload:
{
"run_id": "uuid",
"agent_name": "my-agent",
"status": "completed",
"output": "Agent response..."
}Sync mode waits for the agent to complete and returns the result in the same HTTP response. A traditional request-response pattern.
Best for:
- REST API integrations
- Interactive applications
- When you need immediate results
- Short-running agent tasks
Response:
{
"status": "ok",
"result": {
"run_id": "uuid",
"output": "Response..."
}
}What Agents Receive as Input
When a connector triggers an agent, the incoming data is passed as the agent's input. The exact format depends on the connector type:
The entire JSON body is passed as the agent's input. Form data fields become key-value pairs. Uploaded files are extracted and sent as inline data to the LLM. See HTTP webhook for details.
The message value is parsed as JSON and passed to the agent from Kafka. A _kafka metadata object is appended with topic, partition, offset, timestamp, and key.
The configured prompt is passed as the agent's input on each cron trigger. If no prompt is set, the agent receives an empty payload.
See each connector's documentation page for the full payload format and examples.
Retrieving Results from Inbound Runs
Inbound connectors return immediately with run_ids without waiting for the agent to finish. To get the agent output, you have two options:
Open the run in the Logs tab to inspect the full output, execution traces, and token usage.