When Native Integrations Are Not Enough

Your support system integrates with Slack, GitHub, Linear, Jira, and a dozen other tools. But what about the internal tool your team built last year? Or the CRM that is not on the integration list? Or the custom dashboard where you want support data to appear?

Webhooks solve this. A webhook is a simple HTTP POST request sent to a URL you specify whenever something happens.

How Webhooks Work

When a routing rule fires, you can add a webhook action that sends the conversation data to any URL:

{
  "event": "message_classified",
  "intent": "bug_report",
  "confidence": 0.93,
  "priority": "high",
  "message": "The export feature crashes on files over 10MB",
  "customer_email": "user@example.com",
  "timestamp": "2026-02-15T14:30:00Z",
  "conversation_id": "conv_abc123"
}

Your receiving endpoint can do anything with this data: log it, trigger an internal workflow, update a database, send a notification, create a record in your custom tool.

Common Webhook Use Cases

Custom CRM. If you built your own CRM or use one without a native integration, a webhook can create a support record for every conversation.

Internal dashboards. Send support data to your analytics pipeline. Build custom dashboards showing support volume, intent distribution, and response times alongside your other business metrics.

Monitoring and alerting. Send critical support messages to your monitoring system (PagerDuty, OpsGenie, etc.) alongside your infrastructure alerts.

Custom automation. Trigger any internal process when a specific intent is detected. A data_export request could trigger your export pipeline. A partnership_inquiry could notify your business development team.

Zapier/Make. If you prefer visual automation builders, use a webhook to trigger a Zapier or Make scenario. From there, you can connect to 5,000+ apps without writing code.

Setting Up a Webhook

Step 1: Create an endpoint. This is a URL that accepts POST requests. It could be:

• A Zapier/Make webhook trigger URL
• An AWS Lambda function URL
• A simple Express/Next.js API route
• Any URL that accepts HTTP POST

Step 2: Add the webhook action to a routing rule.

Rule: When intent = partnership_inquiry AND confidence > 75% Action: POST to https://your-api.com/support-webhook

Step 3: Test it. Send a test message that matches the intent and verify your endpoint receives the data.

Webhook Best Practices

Respond quickly. Your webhook endpoint should return a 200 response within 5 seconds. If your processing takes longer, acknowledge the webhook immediately and process asynchronously.

Handle duplicates. Webhooks can fire more than once in rare cases (network retry). Use the conversation ID to deduplicate.

Secure your endpoint. Validate incoming requests. At minimum, check for expected fields. Better: use a shared secret or verify the request signature.

Log everything. Log incoming webhook payloads for debugging. When something goes wrong (and it will eventually), logs are your best friend.

Monitor failures. If your endpoint starts returning errors, you want to know. Set up alerts for webhook delivery failures.

The Power of Webhooks

Webhooks turn your support system from a closed product into an open platform. Any tool, any workflow, any custom process can be triggered by a customer support event. The classification model identifies the intent, the routing rules decide what happens, and webhooks extend those actions to anywhere you need them.