Webhooks work in three directions. Webhook (in) lets another system start a run by POSTing signed JSON to the app's receiver. Webhook (out) posts every finished answer as signed JSON to a URL of yours. And a webhook tool lets the agent trigger your system in the middle of a conversation. All three are recorded: inbound events with their outcome, deliveries as steps, tool calls with request and response.
An order-triage app: your order system posts each new order to Webhook (in), the agent answers, and Webhook (out) posts the triage back to your system, on one thread per order.
A support assistant whose every answer is mirrored to your data warehouse or ticketing system through Webhook (out).
An agent that hands a qualified lead to your automation platform (Zapier, Make, n8n or your own endpoint) through a webhook tool once the user asks to be contacted.
The shape a tool takes in the AgentRow builder API. Credentials are stored on the tool's auth settings, not in its configuration, so they never reach a prompt. Placeholders in double braces are filled by the model from the input schema.
[
{
"id": "webhook_in",
"type": "webhook_in",
"config": {
"integration_id": 3,
"signature_scheme": "agentrow_hmac_sha256",
"replay_window_seconds": 300,
"input_path": "input",
"thread_key_path": "thread_key",
"dedupe_key_path": "event_id"
}
},
{
"id": "webhook_out",
"type": "webhook_out",
"config": {
"integration_id": 3,
"target": "fixed_url",
"url": "https://hooks.example.com/agentrow/answers",
"sign": true,
"include": ["output", "run", "thread"]
}
}
]Every turn shows its channel on the Chat (in) step (source, thread, caller), and every delivery is its own step after Chat (out) with the request, the channel's response, timing and a named error when it failed. Inbound events are listed on the app's Credentials tab with their outcome: accepted, duplicate or rejected, each with its reason.
Yes. Webhook (in) is the receiver: signed JSON starts a run on the thread your payload names. A repeated event id answers 'duplicate' and starts nothing, and unsigned or stale requests are refused by name.
No. Webhook (out) runs after the answer is complete. A failed delivery is a failed step with a named error and the HTTP status; the run keeps its answer and any other delivery still runs. Deliveries are not retried automatically.
The response body is recorded and returned to the model like any tool result, so a synchronous receiver can answer with data. For long-running work, return a job id and let the user ask about it later.
One app graph on every channel: chat widget, end-user API, Slack bot, signed webhooks in and out, and server-to-server runs, each an explicit node.
App tabs, how an app run routes to an agent, and how anonymous and signed-in end users are identified.
Compare AgentRow and LangFlow for AI agents: visual workflows, multi-agent orchestration, RAG, observability and what it takes to run in production.
Slack, HubSpot, Stripe, Shopify, GitHub, calendar, email, wikis, webhooks and any REST API.
Start a free trial and wire it up, or tell us which systems you need to connect and we will point you at the right tool definitions.