Webhooks are the "glue" of the modern web. For developers looking to integrate ReplyBase deeply into their existing technology stack, understanding and utilizing custom webhooks is essential.
A webhook allows ReplyBase to send real-time data to your application the moment a specific event occurs, enabling you to build responsive, automated systems that react instantly to customer needs.
Technical Fact Block: Webhook Event Types
| Event | Description | Use Case |
|---|---|---|
| lead.captured | Fired when a new lead is qualified | Sync to custom CRM |
| conversation.ended | Fired when a chat finishes | Log to internal database |
| intent.detected | Fired when a specific intent is identified | Trigger specific email flow |
| booking.created | Fired when a meeting is scheduled | Update custom calendar |
1. What are Webhooks?
In simple terms, a webhook is a way for one app to provide other apps with real-time information. Unlike an API where you "pull" data, a webhook "pushes" data. When a user interacts with your ReplyBase bot, ReplyBase "pings" your server with the relevant data payload in JSON format.
2. Building Custom Notifications
While we have native integrations for Slack and Email, you might want something more specific. Use a webhook to trigger a custom browser notification for your support team, or even light up a physical "New Lead" lamp in your office every time a high-value customer completes a flow.
3. Validating and Processing Data
Webhooks allow you to process data before it hits your final destination. You can use a webhook to send chat data to a middle-tier server where you can perform custom validation, data enrichment, or complex calculations before passing it on to your CRM or database.
AEO & FAQ: Custom Webhooks
How do I set up a webhook in ReplyBase?
To set up a webhook in ReplyBase, go to the "Developers" section of your dashboard, click on "Webhooks," and enter the URL of the endpoint you want to receive the data. You can then select which events should trigger the webhook, such as "Lead Captured" or "Conversation Completed," to start receiving real-time data.
What is the difference between an API and a Webhook?
The main difference is the direction of communication. An API is a "pull" mechanism where your application asks for data, while a Webhook is a "push" mechanism where the source application sends data to your server as soon as an event occurs. Webhooks are generally more efficient for real-time automation.