Webhooks and delivery

OutboundSync receives webhooks from your sales engagement platform (SEP), processes and matches them, then writes activity and related records into your CRM (HubSpot, Salesforce, or Close — Close is in beta with one-way email and social activity).

Sequence diagram: a sales engagement platform sends a webhook payload to OutboundSync; OutboundSync identifies the contact, then either applies filters and writes activity to the CRM or queues the payload until a match arrives; OutboundSync acknowledges the SEP at the end. — How a webhook payload moves from your sales engagement platform through OutboundSync to your CRM.

For connector-specific URLs, payload shapes, and UI steps, use your SEP’s webhook guide. Use the articles below for platform-wide behavior (forwarding, queueing, testing, and how HubSpot processes payloads).

How OutboundSync handles webhook forwarding Forwarding rules and delivery expectations.

Queueing and prioritization Why some events may arrive in CRM slightly after others.

Sending test webhook payloads Validate configuration before going live.

How webhook payloads are processed (HubSpot) Processing model for HubSpot customers.

Example: Smartlead webhook guide Representative SEP-specific setup (repeat pattern for other tools).