OutboundSync webhooks

When to use this guide: You want OutboundSync to notify your ops stack (PagerDuty, Slack, a custom HTTPS handler) when outbound→CRM sync starts failing or recovers — without polling the API. For how Webhooks sit next to the API and Agent Skills in agentic workflows, see AI and Agents. To diagnose or manage webhooks from a coding agent, install the Sync monitoring Agent Skill.

Inbound paste URLs from your sales engagement platform are Sources. This section is about Webhooks: HTTPS endpoints OutboundSync calls with its own Sync Monitoring events. See Sources and delivery for the inbound Sources → CRM path.

The Webhooks surface is in Beta.

What are OutboundSync webhooks?

OutboundSync webhooks are customer-registered HTTPS URLs that receive OutboundSync-emitted Sync Monitoring events (for example sync.failed and sync.recovered). They are account-level delivery channels managed under Dashboard → Webhooks and via /api/v1/webhooks, distinct from Sources (inbound paste URLs) and Forwarding destinations (raw SEP payload fan-out).

OutboundSync emits Sync Monitoring events and delivers them to your registered HTTPS webhook.

Sources vs Forwarding destinations vs Webhooks

Concept	UI label	API term	What it does
Inbound SEP paste URL (POST /webhooks/:code)	Sources	source	Sequencer posts engagement events into OutboundSync
Forward raw events to customer HTTPS	Forwarding destinations	destination (forwarding)	OutboundSync forwards received SEP payloads to your URL
Reply-CC to a sales rep	Reply relays	destination (reply relay)	Loops a rep into prospect replies
OutboundSync-emitted Sync Monitoring	Webhooks	webhooks	OutboundSync POSTs sync.failed / sync.recovered (and more later) to your URL

Bottom line: Sources ingest; Forwarding destinations and Reply relays are Destinations; Webhooks are OutboundSync’s own alerts about sync health.

Start here

Sync monitoring Agent Skill Diagnose /webhooks and /events from your agent; mutations only after confirmation.

Setting up webhooks Enable Webhooks, register a URL in the dashboard or API, and store the signing secret.

Webhook event types Active sync.failed / sync.recovered events, test.ping, and reserved names.

Webhook payloads and signatures Delivery envelope, headers, and how to verify OutboundSync-Signature.

Webhook delivery and retries Timeouts, retry schedule, auto-disable, and the /events log.

Testing and troubleshooting webhooks test.ping, deliveries, replay, and common 403 / signature failures.

API v1 reference Full request and response contract for /api/v1/webhooks and /api/v1/events.

Frequently asked questions

How do I enable Webhooks on my account?

Ask an OutboundSync admin to enable Webhooks for the account (canUseWebhooks), the same way API access is enabled. Without it, /api/v1/webhooks* and /api/v1/events* return 403.

Are Webhooks the same as Sources or “webhook receivers”?

No. Sources are inbound paste URLs sequencers POST to. Webhooks are OutboundSync→your HTTPS endpoints for Sync Monitoring. Older docs may say “webhook receiver” for Sources during the vocabulary transition.

Do I need a write-scoped API key?

Yes for create, update, delete, rotate-secret, test, and replay. All /api/v1/webhooks* routes also require an account-scoped key (connection-scoped keys get 403). Read-only GETs still need the account-scoped key.

Can I try Webhooks from the docs console?

Not yet from the live menu — production OpenAPI does not list /api/v1/webhooks* or /events today. When those paths ship in OpenAPI, Try the API will show them with path parameters and JSON bodies. Until then, use the Dashboard → Webhooks UI or call the API directly with the samples in the v1 reference.