Integrations
Webhooks
Understand outbound webhook concepts, when to use them, and how they differ from Slack notifications.
Last updated: 2026-03-27
What webhooks do
Tideflow can send event data to a URL you control whenever something happens in your workspace, such as a new call being handled or a caller record being created. These outbound HTTP requests are called webhooks.
Webhooks let you build custom workflows, push data into your own systems, or integrate with tools that Tideflow does not have a built-in integration for.
Webhooks vs Slack
| Slack integration | Webhooks | |
|---|---|---|
| Destination | A Slack channel | Any HTTPS endpoint you control |
| Format | Formatted Slack message | Structured JSON payload |
| Best for | Team awareness and quick review | Custom integrations and automation |
| Technical effort | Low (just paste a URL) | Moderate (you need a receiver endpoint) |
How to set up webhooks
1. Prepare your endpoint
Create an HTTPS endpoint that can receive POST requests with a JSON body. This could be a serverless function, a backend API route, or an automation platform like Zapier or Make.
2. Add your webhook URL in Tideflow
- Open your Tideflow dashboard and go to Settings → Integrations.
- Find the Webhooks section and enter your endpoint URL.
- Choose which events should trigger webhook delivery.
- Save the configuration.
3. Verify delivery
Use the test button to send a sample event to your endpoint. Check that your receiver responds with a 200 status code and processes the payload correctly.
Event payload
Each webhook delivery is a POST request with a JSON body that includes:
- An event type identifier
- The relevant data (caller details, call summary, timestamps)
- A delivery timestamp
The exact payload shape depends on the event type. Detailed event documentation is coming in the Developers section.
Security
Webhook deliveries can include an HMAC signature header so you can verify that the request came from Tideflow and was not tampered with. Check the developer documentation for signature verification details (coming soon).
Delivery expectations
- Tideflow delivers webhooks as soon as the event is processed. Most deliveries happen within seconds.
- If your endpoint returns a non-success status code, Tideflow may retry the delivery.
- Persistent failures are logged and visible in your integration settings.
When to use webhooks
Webhooks are the right choice when you want to:
- Push call data into a CRM, database, or analytics system
- Trigger custom automations when a call is handled
- Build dashboards or reports from Tideflow event data
- Integrate with tools that are not covered by built-in integrations