Skip to content
Webhooks & Enrichment
🔍 Data Enrichment
Automatically fill in extra contact info and data for your client records.
✨ Enrichment Features
| Feature | Description |
|---|---|
| Phone Append | Find extra phone numbers for a client |
| Email Append | Discover email addresses |
| Address Append | Find or verify addresses using reverse phone/email lookup |
| Demographics | Add demographic info |
⚡ Enrichment Triggers
Choose when enrichment happens:
| Trigger | Description |
|---|---|
| On Call | Enrich when making a call |
| On SMS | Enrich when sending a text |
| On Import | Enrich when importing records |
| Manual | Enrich whenever you want |
🛠️ Setting Up Enrichment
- Go to Settings → Integrations
- Select Data Enrichment
- Set up your enrichment provider
- Pick your automatic triggers
- Choose which data to add
📊 Enrichment History
See all enrichment attempts:
| Field | Description |
|---|---|
| Date | When it happened |
| Type | What data was looked up |
| Status | Did it work or not |
| Data Found | What info was discovered |
| Cost | Credits or money used |
🔔 Webhook Integrations
Send data to other systems whenever something happens in Kayse AI.
🤔 What Are Webhooks?
Webhooks are like automatic messages sent to other websites when things happen. They let you:
- Get notified about events in real time
- Build custom automations
- Connect with any system that can receive webhooks
🛠️ Setting Up Webhooks
- Go to Settings → Webhooks
- Click Add Webhook
- Enter the destination URL (where to send the data)
- Pick which events should trigger the webhook
- (Optional) Filter by campaigns — only available for call events
- Set up security (optional)
- Save and test it
Note: Campaign filters only work with call events (started, ended, analyzed). Message and task events are always sent across all campaigns.
📋 Available Events
| Category | Events |
|---|---|
| Cases | Created, Updated, Status Changed, Deleted |
| Clients | Created, Updated, Merged, Opt-Out Changed |
| Calls | Started, Completed, Failed, Transferred |
| Messages | Sent, Received, Failed |
| Tasks | Assigned, Completed, Overdue |
| Forms | Submitted |
| Campaigns | Started, Paused, Completed |
📦 Webhook Payload
Webhooks send data as JSON. Here's an example:
json
{
"event": "case.updated",
"timestamp": "2024-01-15T10:30:00Z",
"data": {
"id": "case_123",
"name": "Smith Case",
"status": "Active",
"changes": {
"status": {
"old": "New",
"new": "Active"
}
}
}
}🔐 Authentication Options
| Method | Description |
|---|---|
| None | No security added |
| API Key | Adds a key in the header |
| Basic Auth | Uses a username and password |
| Bearer Token | Uses a JWT or OAuth token |
| HMAC Signature | Signs the data so the receiver can verify it |
⚙️ Webhook Management
| Action | Description |
|---|---|
| Enable/Disable | Turn a webhook on or off |
| Test | Send a test message to check it works |
| View Logs | See the delivery history |
| Retry Failed | Resend messages that didn't go through |
🔄 Retry Logic
If a webhook fails, Kayse AI tries again automatically:
| Attempt | Wait Time |
|---|---|
| 1 | Right away |
| 2 | 5 minutes |
| 3 | 30 minutes |
| 4 | 2 hours |
| 5 | 24 hours |