Generic webhook integration
If your tool isn’t in the integration catalog, use a generic webhook to send events from Active Reach to any HTTPS endpoint.
Setup
- Go to Settings → Data Pipes → New → Generic Webhook
- Enter your endpoint URL (must be HTTPS)
- Select which events to send (same event types as outbound webhooks)
- Configure authentication:
- None — no auth header (not recommended for production)
- Bearer token —
Authorization: Bearer <your-token> - Custom header — any header name and value
- Test the connection and activate
Payload format
Same JSON structure as the webhook payload format:
POST https://your-endpoint.com/webhook
Content-Type: application/json
Authorization: Bearer <your-token>
{
"id": "evt_a1b2c3d4",
"type": "delivery.delivered",
"timestamp": "2026-04-17T10:30:00.000Z",
"workspace_id": "ws_abc123",
"data": { ... }
}Use cases
- Internal dashboards — pipe delivery events to your own analytics backend
- Slack notifications — forward campaign completion events to a Slack webhook
- Custom CRM — sync contacts to a CRM that isn’t natively supported
- Audit/compliance — archive events to an internal logging service
- ETL pipelines — feed into Apache Airflow, Prefect, or similar
Retry behavior
Generic webhooks use the same retry policy as standard webhooks — 6 retries with exponential backoff, 7-day DLQ retention.
What’s next
- Webhook event types — full event catalog
- Integrations overview — all native integrations