RobofyAI Agent Webhooks for Your Business Workflows
Send Lead Capture, Human Handoff, and Session End events from Robofy to your HTTPS endpoint. Use the event data in your own CRM, support, reporting, automation, or internal workflows, with subscriptions configured for each AI Agent.
Conversation happens in Robofy
Your app verifies, then decides what happens next
What Are AI Agent Webhooks?
AI agent webhooks are HTTP notifications that send supported AI conversation events from Robofy to an external HTTPS endpoint.
Something meaningful happens
When Lead Capture, Human Handoff, or Session End occurs, Robofy prepares the corresponding webhook payload for that AI Agent.
Robofy notifies your endpoint
The payload is sent to the HTTPS endpoint configured for that agent. Lead Capture and Human Handoff can occur while the conversation is still active.
Your system decides what happens next
Your receiving application owns the outcome. Robofy does not directly update your CRM or helpdesk - your workflow does.
Your endpoint might…
- Create or update a CRM record
- Notify a support team
- Open a ticket
- Store conversation information
- Trigger an automation
- Send data into an analytics or reporting workflow
The AI conversation happens in Robofy. Webhooks carry important conversation events into the rest of your business workflow.
Choose Which AI Agent Events Your Webhook Receives
Subscribe each webhook to the events relevant to the workflow connected to that endpoint.
Event 01 · Sales & follow-up
Lead Capture
Move captured leads into your follow-up workflow
Send captured lead information and available conversation context to your endpoint when the AI Agent creates a Lead Capture event. Your system can use that information to create or update records, route leads, or begin the next sales workflow.
- Captured lead fields, source and context information, and capture timing when available.
- Session reference when available, so the lead can be traced back to its conversation.
"event": "lead.captured",
"lead": { "email, phone, fields…" },
"context": { "source, timing, session…" }
}
Event 02 · Support & escalation
Human Handoff
Give your support workflow the context it needs
Send handoff context to your endpoint when a handoff request is created, including details such as the reason, conversation summary, preferred contact method, and available customer contact information. Your system can use the event to create a support ticket, notify a team, or start another escalation workflow.
- Handoff reason, conversation summary, and preferred contact method when available.
- Available customer contact details - only fields the conversation actually captured.
"event": "handoff.created",
"reason": "billing dispute",
"summary": "2 failed payments…",
"contact": { "whatsapp, email…" }
}
Event 03 · Reporting & analysis
Session End
Send completed session context into reporting and analysis workflows
When a conversation becomes eligible for Session End processing after the configured inactivity threshold, Robofy can send session information and a text transcript to your endpoint. Your system can then store or process that information for reporting, analytics, review, or other internal workflows.
- Standard payload: agent reference, session reference, and text transcript.
- The inactivity threshold is shared per agent - see the timer section below.
"event": "session.ended",
"agent": { "reference…" },
"session": { "reference…" },
"transcript": "text…"
}
Payload contents can vary depending on the event and the information available in the conversation.
Set One Session End Timer for Your AI Agent
Choose how many minutes a conversation must remain inactive before it becomes eligible for Session End processing. The Session End timer belongs to the event configuration of the AI Agent, not to an individual webhook. Every webhook on the same AI Agent that subscribes to Session End uses the same inactivity threshold.
Agent A - shared 15-minute thresholdChanging this value updates every Session End subscription on that agent.
What happens as inactivity grows
Processing runs through the platform background workflow. Treat the timer as an eligibility threshold, not an exact dispatch deadline.
- 1Active conversationMessages are still flowing. The timer has not started.
- 2InactiveNo new messages. Inactivity time starts accumulating.
- 3Eligible for Session EndInactivity period reached. Session becomes eligible for processing.
- 4Webhook sentSubscribed endpoints receive session data via background processing.
Configure Your AI Agent Webhook
A webhook configuration holds a name, URL, optional secret, timeout, event subscriptions, and an Active / Inactive state - managed per AI Agent, after creation, as operational control.
Name
Give the webhook a recognizable name for the workflow or destination.
URL https://
Enter the HTTPS endpoint where Robofy should send subscribed events.
Secret optional
Add an optional secret for request verification via payload signing.
Timeout
Choose how long Robofy should wait for the receiving endpoint.
Events
Subscribe to one or more supported events: Session End (Inactivity), Human Handoff, Lead Capture.
Active / Inactive
Control whether the webhook is currently active without removing its configuration.
From endpoint to first event
- Prepare an HTTPS endpoint that accepts webhook requests.
- Create a webhook for the required AI Agent.
- Enter the name, URL, optional secret, and timeout.
- Select Lead Capture, Human Handoff, Session End, or a combination.
- Configure the Session End inactivity timer if Session End is selected.
- Trigger a relevant event and confirm that your endpoint processes the payload.
Verify Webhook Requests Before Processing Them
Add an optional secret to enable HMAC-SHA256 payload signing. Your endpoint can verify the signature in the X-Hub-Signature-256 header before processing the event.
Should You Use a Webhook or a Function Tool?
Both connect your AI Agent to external systems, but the direction and purpose of the integration are different.
Function Tool Calling
Use a Function Tool when the AI Agent needs to call an API, retrieve data, perform an action, and potentially use the result during the conversation.
AI Agent → Order API → order status → AI Agent answers customer
AI Agent → booking API → action completed → AI Agent confirms result
AI Agent Webhooks
Use a webhook when Robofy needs to notify an external system that a subscribed conversation event occurred.
lead captured → endpoint → sales workflow
handoff request created → endpoint → support workflow
session eligible → endpoint → reporting workflow
The agent reaches out mid-conversation and uses the API response in its next answer.
Robofy pushes subscribed events out - your workflow decides what happens next.
Different Agents, Different Endpoints
Users can create different webhooks for individual AI Agents, and different webhooks may subscribe to different events.
Sales AI Agent
Qualifies and captures demandSupport AI Agent
Escalates with full contextConversation session
Closes the loop on every chatFrequently Asked Questions
What AI Agent events can trigger a webhook?
Robofy currently supports Lead Capture, Human Handoff, and Session End webhook events. Each webhook can subscribe to the events required by its connected workflow.
Can I use different webhooks for different AI Agents?
Yes. Webhooks are configured for individual AI Agents, allowing different agents to send events to different endpoints and workflows.
Can one webhook subscribe to multiple events?
Yes. A webhook can subscribe to the supported events required by that endpoint. You can also configure additional webhooks when different destinations should receive different events.
Does a webhook automatically update my CRM or helpdesk?
Robofy sends the subscribed event to your HTTPS endpoint. Your receiving application or automation decides how that data is mapped and what action happens next.
When is the Session End webhook sent?
The configured inactivity period determines when a session becomes eligible for Session End processing. Session processing occurs through the platform background workflow, so the timer should be treated as an inactivity threshold rather than an exact dispatch deadline.
Is the Session End timer configured separately for each webhook?
No. The Session End timer belongs to the event configuration of the AI Agent. Webhooks on that agent that subscribe to Session End share the same inactivity threshold.
Does Human Handoff automatically transfer the live conversation to a person?
The webhook notifies your external workflow when a handoff request is created and can provide available handoff context. The webhook itself does not determine how your organization assigns or handles the follow-up.
Can my AI Agent use the webhook response in its next message?
AI Agent webhooks are event notifications. If the agent needs to call an API and use the response during the conversation, use Function Tool Calling instead.
Can webhook requests be verified?
Yes. When a secret is configured, Robofy supports HMAC-SHA256 payload signing. Your receiving endpoint can verify the signature before processing the event.
What information is included in a webhook?
The payload depends on the selected event and the information available in the conversation. Lead Capture can contain captured lead information and context, Human Handoff can include escalation context and available customer details, and the standard Session End payload includes session information and a text transcript.
Notify your systems when AI Agent events occur.
Create Your AI Agent