Skip to content

Clay

When to use this guide: Read this before configuring Clay’s native email sequencer with OutboundSync to confirm what gets synced and how setup works.

OutboundSync supports Clay’s native email sequencer as an engagement source for HubSpot and Salesforce. Clay’s sequencer runs on a Smartlead white-label, so Clay sends webhook events to OutboundSync through the standard Smartlead webhook receiver.

What this integration does

Section titled “What this integration does”

When you launch a sequence from a Clay table using Clay’s native sequencer, Clay sends Smartlead-format webhook events to a webhook receiver URL you configure inside Clay. OutboundSync handles those events the same way it handles any Smartlead campaign — writing sends, replies, opens, clicks, and bounces onto the matching HubSpot or Salesforce record.

You can use Clay as the sole source of outbound, or run it alongside a separate Smartlead account. Each Clay table connects to its own webhook receiver, so client or campaign data stays cleanly separated.

What syncs into your CRM

Section titled “What syncs into your CRM”

Clay’s sequencer emits Smartlead-format events. The supported events are:

  • Email sends and manual email sends
  • Opens
  • Link clicks
  • Replies and reply-category updates
  • Bounces
  • Unsubscribes

Campaign, sequence step, and timestamp metadata are preserved on each activity record.

Where it syncs

Section titled “Where it syncs”
  • HubSpot — direct integration
  • Salesforce — direct integration
  • Close — supported during the current Close beta

See Clay + HubSpot and Clay + Salesforce for the destination-specific field mappings.

Setup

Section titled “Setup”

Setup uses the standard Smartlead webhook receiver path:

  1. Generate a Smartlead-style webhook receiver URL in OutboundSync.
  2. Paste that URL into the webhook field on your Clay sequence.
  3. Confirm the first events arrive and land on the right CRM record.

For reference, see the Smartlead webhook guide and Connect your Smartlead API key — the Clay path follows the same setup mechanics.

Scope and current limitations

Section titled “Scope and current limitations”
  • One-way sync. Data flows Clay → CRM. Updates in HubSpot or Salesforce are not written back to Clay.
  • Email channel only. Clay’s sequencer is email today; phone and social events are out of scope here.
  • Smartlead-format events. Clay only emits the Smartlead-format events listed above. Clay table fields, AI research outputs, and enrichment data are not synced as separate webhook events — write those to your CRM from inside the Clay table directly.
  • Guided setup. Initial wiring is handled with the OutboundSync team during onboarding.

Get help and next steps

Section titled “Get help and next steps”