Can a webhook return data to the agent?
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.
When the target is your own service, an automation platform or a queue, a webhook is the simplest integration: the agent posts an event with a payload and your system does the rest. AgentRow's webhook tool sends the event, records the request and response, and applies the same limits as any other tool.
An agent that hands a qualified lead to your automation platform (Zapier, Make, n8n or your own endpoint).
A workflow agent that enqueues a long-running job and tells the user it has been started.
A support agent that raises an incident in your on-call system when a conversation matches an outage pattern.
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.
{
"name": "notify_lead_pipeline",
"type": "webhook",
"description": "Send a qualified lead to the sales pipeline. Use once the user has shared a name, company and email and asked to be contacted.",
"auth_type": "custom_header",
"safety_level": "write_safe",
"config": {
"url": "https://hooks.example.com/agentrow/leads",
"event_name": "lead.qualified"
},
"input_schema": {
"type": "object",
"properties": {
"name": { "type": "string" },
"company": { "type": "string" },
"email": { "type": "string" },
"summary": { "type": "string", "description": "One-paragraph summary of what the lead needs" }
},
"required": ["name", "email"]
}
}Every call appears in the run trace with the rendered request, the response status and body, timing, retries and errors, plus what the model was shown of the result. If the model never called the tool, the toolbox step shows whether it was bound for that model call and why.
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.
Set max calls per tool on the toolbox, use rate limits, and make the description explicit about when to trigger. The most recent tool-calling turn is replayed to the model so it knows what it already sent.
Runs start from messages today, through the widget or the end-user API. Your webhook receiver can call that API to start a conversation.
Connect AI agents to HTTP APIs, webhooks, web pages and other agents with typed tools: JSON schemas, auth types, safety levels, limits and call logs.
Tool types, what a tool defines, how results reach the model, tool selection with search_tools, and authenticated tools for signed-in users.
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.
Join the waitlist for early access. Tell us which systems you need to connect and we will point you at the right tool definitions.