Webhooks
Hunch can send webhook notifications to your server when important actions complete on your website. This lets you integrate Hunch outcomes into your CRM, Slack, email workflows, or any system that accepts HTTP webhooks.
Setting up webhooks
- Go to your website settings in the Hunch dashboard.
- Enter your webhook URL in the Webhook URL field. The URL must use HTTPS.
- Save your settings.
Hunch will send a POST request to your webhook URL whenever an action completes.
Webhook payload
{
"event": "action.completed",
"website_id": "ws_abc123",
"outcome_type": "lead_captured",
"outcome_status": "completed",
"outcome_label": "Contact Form Submission",
"source_type": "mcp",
"session_id": "sess_xyz",
"metadata": {
"toolName": "contact_form",
"executionMode": "browser_public"
},
"timestamp": "2026-04-22T14:30:00.000Z"
}
Outcome types
| Type | When it fires |
|---|---|
lead_captured | A contact or lead form was submitted |
meeting_booked | A booking or demo was scheduled |
quote_requested | A quote or estimate request was submitted |
search_completed | A search action completed |
checkout_started | A checkout flow was initiated (live bridge) |
handoff_exported | An action session was exported as a handoff |
Headers
| Header | Value |
|---|---|
Content-Type | application/json |
User-Agent | Hunch-Webhooks/1.0 |
X-Hunch-Event | action.completed |
Retry policy
Hunch sends webhooks on a best-effort basis. If your endpoint returns a non-2xx status code, the delivery is logged as failed but not retried. Ensure your endpoint responds within 10 seconds.
Testing webhooks
Use a service like webhook.site or RequestBin to test your webhook URL before connecting it to your production system.