Webhook Settings

Workspace webhooks send real-time JSON events from OutCallerAI to an HTTPS endpoint you control. Use them to sync leads, calls, tasks, and agent changes into your CRM or internal systems.

Configure Webhooks

1. Open Integrations.
2. Click Webhook Settings.
3. Enter your Webhook URL.
4. Optionally enter Webhook Headers (JSON) for auth or routing.
5. Save changes.

Headers must be a JSON object:

{
	"Authorization": "Bearer your-secret-token",
	"X-CRM-Source": "outcaller"
}

OutCallerAI sends these headers on every webhook:

Your configured custom headers are merged into the request.

Events

Common events include:

Payload

Every webhook request is a POST with this envelope:

{
	"event": "lead.created",
	"resource": "lead",
	"action": "created",
	"workspaceId": "cmpxz43bl00032c6udndznzdg",
	"timestamp": "2026-06-04T05:49:10.221000+00:00",
	"data": {
		"id": "lead_123",
		"workspaceId": "cmpxz43bl00032c6udndznzdg",
		"campaignId": "campaign_123",
		"name": "Priya Sharma",
		"phone": "+919876543210",
		"email": "priya@example.com",
		"source": "google_sheet_webhook",
		"status": "new"
	},
	"metadata": {
		"source": "google_drive_sync"
	}
}

Update events may include previousData.

Data Included

Webhook payloads are sanitized before delivery. OutCallerAI includes useful operational fields such as ids, workspace/campaign links, lead contact fields, call status, call summary, transcription, recording URL, task status, and timestamps. Internal secrets and provider-only fields are not sent.

Delivery Behavior

• OutCallerAI sends each webhook as an HTTPS POST.
• The request timeout is 10 seconds.
• Your endpoint should return any 2xx response.
• Failed deliveries are logged by OutCallerAI.

Endpoint Tips

• Use HTTPS in production.
• Keep responses fast; offload slow work to a queue.
• Make handlers idempotent by storing processed event ids or deduplicating by event, resource, data.id, and timestamp.
• Validate your own auth header if you configure one in Webhook Headers (JSON).