Sources and delivery

OutboundSync receives Sources (inbound paste URLs) 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).

This page covers inbound Sources → CRM delivery. Separately, OutboundSync can emit its own Webhooks (Sync Monitoring — for example sync.failed / sync.recovered) to HTTPS endpoints you register. That surface has its own docs: OutboundSync webhooks. The API contract lives under Webhooks in API v1.

Sequence diagram: a sales engagement platform sends an event to an OutboundSync Source; 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 an inbound Source event 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, reply relays, queueing, testing, and how HubSpot processes payloads).

How OutboundSync handles webhook forwarding Forwarding rules and delivery expectations.

Setting up reply relays Loop a sales rep into Smartlead or EmailBison prospect replies.

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).