Partner spotlight: Clay
Clay Sequencer is Clay's native outbound engine. See how OutboundSync syncs its send and reply activity, one-way, into your Salesforce or HubSpot records.
Jason Ma
Clay → Close
Clay + Close integration
Clay finds and enriches the prospect, the sequence starts the conversation, and Close is where reps finish it. OutboundSync logs each Clay sequence event on the Close Lead.
BetaOne-way syncEmail
Clay + Close at a glance
Clay's native sequencer works with Close through OutboundSync. Sequence sends, manual sends, opens, link clicks, replies, reply categories, bounces, and unsubscribes from Clay are logged as activity on the matching Close Lead. The sync is one-way, Clay into Close, and the OutboundSync team handles setup with you.
| Status | Beta (Close is a one-way beta CRM) |
|---|---|
| Channels | |
| Direction | One-way, Clay → Close |
| Close records | Leads |
| Block lists | Not available for this pairing |
| Clay plan | Any plan with Sequences |
| Setup | Guided: the OutboundSync team runs onboarding |
Clay-built lists are often small, targeted, and expensive to research, so every reply counts. When those replies stay inside Clay, reps in Close miss them or find them late. OutboundSync sends each sequence event to the Close Lead, so the rep sees the reply and the emails that led to it.
Reply categories come through too. A Close Smart View filtered to interested replies from Clay campaigns turns a well-researched list into a prioritized call queue, without anyone exporting from Clay.
What syncs from Clay to Close
Every event below arrives in near-real time and lands on the matched Close record. Pick the ones you want per source.
| Event | Channel | Where it lands in Close |
|---|---|---|
| Email sent— Sequence sends and manual sends from Clay | Activity on the Close Lead | |
| Email opened | Activity on the Close Lead | |
| Link clicked | Activity on the Close Lead | |
| Reply received | Activity on the Close Lead | |
| Email bounced | Activity on the Close Lead | |
| Lead unsubscribed | Activity on the Close Lead | |
| Lead category updated— Smartlead's built-in and custom lead categories | Activity on the Close Lead |
Event names come from the Clay webhooks OutboundSync receives. Close is a one-way beta, so exact event coverage is confirmed during onboarding. See the Clay event reference.
What teams do with Clay + Close
Call researched replies first
Smart Views on Clay reply categories put interested prospects at the top of the queue.
Keep sequence context
Every Clay email the prospect received is visible on the Close Lead before the first call.
Separate tables cleanly
Each Clay table uses its own source, so segments stay distinct in Close activity.
Ways to connect Clay and Close
The options teams weigh before they commit a production sync.
| Option | What it does | Trade-off |
|---|---|---|
| Zapier, Make, or n8nCompare integration platforms | Catch Clay webhooks and write each event to Close with a workflow you build. | Every event type, retry, and field change is a workflow you maintain, billed per task or step. |
| Custom buildBuild vs buy | Write your own service against the Clay and Close APIs. | You own matching, deduplication, API limits, and every upstream schema change. |
| OutboundSync | Pre-built email activity sync into Close Leads. | One-way beta with guided onboarding. Lighter configuration than HubSpot or Salesforce today. |
How to set up Clay + Close
Step 1: Connect Close
Authorize OutboundSync from the Close App Marketplace. The OutboundSync team adds Close as a Connected Account with you.
Step 2: Connect Clay
Create a Smartlead-style source in OutboundSync and paste its URL into the webhook field on your Clay sequence.
Step 3: Create the Close source
Select Clay when you create the Close source, and confirm how contacts are matched.
Step 4: Send a test event
Trigger one Clay event and confirm it on a real Close Lead.
Step 5: Go live
Launch with the OutboundSync team watching the first production events in Close.
Plan requirements
Clay plan
Any plan with Sequences
OutboundSync works with every Clay plan, because it connects to Clay's native sequencer rather than a plan-gated feature.
Close
Close is a one-way beta. There is no Close plan gate on our side; onboarding runs with the OutboundSync team.
Related integrations and guides
Clay with other CRMs
Other outbound tools for Close
Trusted by outbound teams
Redis
Windsurf
Gainsight
Sendoso
Crescendo
TapcheckClay + Close FAQ
What Clay activity does OutboundSync sync to Close?
Email sent, email opened, link clicked, reply received, email bounced, lead unsubscribed, and lead category updated.Which Close records does it write to?
OutboundSync matches or creates Close Leads. Clay events land as activity on the Close Lead. See the Close beta guide for details.Does Clay social or phone activity sync to Close?
No. Clay's sequencer is email only today, so OutboundSync syncs email events. Those channels need their own tool connected to OutboundSync.Is the integration one-way or two-way?
One-way. Activity flows from Clay into Close, and nothing is written back to Clay.Can I use Close records as a block list?
Not today. Block lists come from HubSpot lists or Salesforce reports. The Close beta syncs activity in only.Do I need admin access to set it up?
A Close admin authorizes OutboundSync from the Close App Marketplace during guided onboarding.Which Clay plan do I need?
OutboundSync works with every Clay plan, because it connects to Clay's native sequencer rather than a plan-gated feature.How is Clay + Close priced?
Beta access is scoped with the OutboundSync team during onboarding. Billing follows the same model as every plan: sent messages per month. Replies, opens, clicks, and lead-category updates are not billed. See the pricing page.Can I do this with Zapier, Make, or n8n?
You can wire simple Clay automations with a no-code builder, but step-based runs get costly and fragile as volume grows. OutboundSync gives you a pre-built path for Clay sequencer events, searchable event logs beyond 30 days, and pricing tied to outbound volume.What breaks first when this scales?
Data quality and reliability break first: duplicate events, retries, out-of-order webhooks, and bursts during big sends. OutboundSync handles idempotency, timing buffers, and queue recovery, and flags suspicious or mismapped payloads instead of writing them.
Clay resources
Tutorials, case studies, and updates related to Clay.
OutboundSync supports the new Clay native email sequencer
See how OutboundSync supports Clay's new native email sequencer, enabling integrated outbound campaign management with HubSpot and Salesforce.
Harris Kenny
Enriching HubSpot with Clay (Part 4: Company Names)
Learn how to enrich HubSpot company names using Clay, ensuring clean, consistent records with a cost-effective provider waterfall.
Harris Kenny
See Clay activity in Close
A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.
