Slack & Teams Alerts
Notify your team instantly when a visitor starts a chat, submits a lead form, or reaches a critical workflow step. No more missed opportunities.
Webhook Integration
For Live Chat Workflows
Send real-time HTTP notifications to any external service when visitors reach a step in your chat workflow. Trigger Slack messages, Discord alerts, Microsoft Teams notifications, CRM record updates, or any API endpoint — all fire-and-forget, never blocking the conversation.
- No credit card
- 14-day free trial
- UK hosted
- Visual builder
What Is the Webhook Integration Module?
The Webhook Integration module sends an HTTP POST request to any URL you specify whenever the workflow reaches that step. It packages up the conversation data — visitor name, email, collected form fields, workflow metadata — and delivers it as a JSON payload to your chosen endpoint. The request is fire-and-forget: it executes in the background and the chat conversation continues immediately without waiting for a response.
This makes webhooks the perfect bridge between your chat workflow and the rest of your technology stack. When a high-value lead fills out a form in the chat, a webhook can instantly notify your sales team on Slack. When a support conversation ends, another webhook can update the customer's record in your CRM. When a visitor requests a callback, a webhook can create a task in your project management tool. The possibilities are limited only by what your external services can accept.
Because webhooks are non-blocking, visitors never experience a delay. The HTTP request fires asynchronously behind the scenes while the chat moves seamlessly to the next step. Even if the external service is slow or temporarily unavailable, the conversation is never interrupted — the webhook simply retries automatically.
CRM Updates
Push visitor data directly into Salesforce, HubSpot, Pipedrive, or any CRM that accepts webhooks. Keep your sales pipeline in sync with live chat activity.
Automation Triggers
Connect to Zapier, Make (Integromat), or n8n to trigger complex multi-step automations. A single webhook can cascade into email sequences, SMS alerts, and database updates.
Analytics & Logging
Send conversation events to your analytics platform or custom logging service. Track funnel progress, drop-off points, and conversion rates in real time.
How the Webhook Module Fits Into a Workflow
Webhooks are invisible to the visitor — they fire silently between steps. The most common pattern is to place a Webhook node immediately after a data collection step (like Collect Info or a Form Field) to forward the captured data to an external service. You can also place webhooks at the end of a workflow to log the outcome, or at the start to notify your team that a new conversation has begun.
You can use multiple Webhook nodes in a single workflow. For example, the first webhook notifies Slack when a visitor provides their details, and the second webhook updates your CRM when the conversation is marked as resolved. Each webhook node operates independently with its own URL, headers, and payload configuration.
Example: Lead Capture With Slack Notification
A B2B company captures leads in the chat and instantly alerts the sales team on Slack.
START
Human Chat
Sales team
Step-by-Step Breakdown
- Collect Info: The workflow gathers the visitor's name, email address, and company name through conversational prompts.
- Webhook to Slack: Immediately after collection, a webhook fires a POST request to the Slack incoming webhook URL. The sales channel receives a formatted message with the lead's details.
- Transition Message: A message reassures the visitor that they're being connected, maintaining a smooth conversational feel.
- Human Chat: The visitor is routed to the sales team, who already have the lead's information displayed in Slack before they even accept the chat.
Best Practices & Tips
Webhooks are powerful integration tools. Follow these practices to ensure reliability and security.
Use HTTPS Endpoints
Always use HTTPS URLs for your webhook endpoints. This ensures that visitor data is encrypted in transit. Never send personal information over unencrypted HTTP connections.
Test With a Receiver First
Use a service like webhook.site or RequestBin to test your webhook configuration before connecting to production systems. Verify the payload structure and headers are correct.
Send Only Needed Data
Configure your webhook payload to include only the fields your external service requires. Minimising data transfer improves performance and reduces privacy exposure.
Plan for Failures
External services can go down. The webhook module retries failed requests automatically, but always have a fallback — such as email notification — for critical workflows.
Frequently Asked Questions
Does the webhook block the chat conversation?
No. Webhooks are fire-and-forget. The HTTP request is sent asynchronously in the background, and the chat conversation moves to the next step immediately. Visitors never experience a delay, even if the external service takes time to respond.
What data is included in the webhook payload?
The payload includes all data collected by the workflow up to that point — visitor name, email, custom form fields, page URL, and workflow metadata. You can customise the payload in the webhook node configuration to include only the fields you need.
Can I add custom headers to the webhook request?
Yes. The webhook configuration supports custom HTTP headers. This is commonly used for authentication tokens, API keys, or content-type specifications required by the receiving service.
How is the webhook different from the API Form module?
The Webhook module is fire-and-forget — it sends data but does not wait for or display a response. The API Form module sends data AND waits for a response, displaying it in the chat. Use webhooks for notifications; use API Form when you need the response.
Related Modules
The Webhook module integrates seamlessly with these modules for powerful connected workflows.
Connect Your Chat to Everything
Add webhook integrations to your workflow in minutes. Notify Slack, update your CRM, trigger automations — all from within the chat conversation, no code required.