---
name: clay-smartlead-integration
description: Connect Clay and Smartlead: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, lists. Use when the user wants to set up, audit or troubleshoot Clay and Smartlead together, or asks why data is not moving between them.
---

# Clay and Smartlead

> Generated from https://www.reversecontact.com/integrations-hub/clay-integrations/clay-smartlead-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** Clay Launch or above, a Smartlead API key, and a campaign that already exists

**What moves:** contacts, lists, one way, out of Clay.
**How it is built:** native, built on the api. **Effort:** minutes.

## The short version

The most complete of the three sending-tool integrations on the Clay hub, because it closes a loop the others leave open: as well as pushing an enriched lead into a campaign, it can look the lead up, update it and remove it. That makes the table a place where disqualification happens rather than only qualification, which matters more than it sounds. The constraints are the familiar ones. The campaign has to exist in Smartlead first, authentication is an API key rather than OAuth, and no reply or bounce data comes back into the table.

## Which Clay plan reaches which kind of tool

Rows: Clay plan. Columns: What you are connecting. Clay does not price this integration by itself. It sorts every integration into a plan band, and the bands are not where most people expect: a data provider costs nothing extra, a sequencer starts one tier up, and a CRM starts two.

| Clay plan | Data providers, like Apollo | Sequencers: Smartlead, lemlist, Outreach | CRMs: HubSpot, Salesforce |
|---|---|---|---|
| Free | Included | Not included | Not included |
| Launch | Included | Included | Not included |
| Growth | Included | Included | Included |
| Enterprise | Included | Included | Included |

- **Included.** Clay's integration catalogue states the band per integration: Apollo reads Included in All Plans, Smartlead, lemlist and Outreach all read Included in Launch+, and the plan comparison marks CRM integrations as included from Growth.
- **Not included.** Not available on that plan at any volume. Every action on all four of these integrations is also marked Bring Your Own Account Required, so the vendor account is a separate prerequisite from the Clay plan.

Counted off that grid, of twelve pairings: nine give you included, three give you not included.

This pair sits in the middle column, which is the least painful of the three gates: Launch is the entry paid plan, so anybody already paying Clay has it. Worth knowing anyway, because a team evaluating the whole chain on the Free plan can test the enrichment and not the thing the enrichment was for.

## What actually syncs

Direction is written from Clay's point of view: out means out of Clay, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| New leads | One way, out | Add lead to campaign, with the campaign chosen from a dropdown populated from your Smartlead account, plus email, name, phone, website and LinkedIn URL. |
| Existing leads | One way, out | Update lead details on a lead already in a campaign, across the same field set. |
| Lead status | One way, in | Look up a lead to read its status and details, which is how a table checks state before acting again. |
| Disqualified leads | One way, out | Remove a lead from a campaign, in the same pass as the enrichment that disqualified them. The capability the other sending pairs here lack. |
| Campaigns | Events only | Not created from Clay. Every action requires an existing Smartlead campaign. |
| Replies, bounces and opens | Events only | Not returned to the table. Smartlead's webhooks post those to an endpoint you control instead. |

## Which field lands where

Six actions, and the thing that decides how you wire them is which identifier each one needs. Two work from an email address and four need Smartlead's internal Lead ID, which only the lookup can give you.

| In Clay | In Smartlead | What to know about the match |
|---|---|---|
| Add lead to campaign | Campaign ID and email, everything else optional | Takes first and last name, phone, website, LinkedIn URL, location, company name and company URL, plus arbitrary custom fields as key-value pairs. Confirms success and returns no fields. |
| Lookup lead in campaign | Email address | The entry point for everything else. Returns the Smartlead Id, the created date, custom fields, Is Unsubscribed, and Lead Campaign Data listing every campaign the lead is in. |
| Lookup lead status in campaign | Campaign ID and email | Returns number of campaign steps, number of sent emails and a status such as IN_PROGRESS. Progress rather than engagement. |
| Update lead in campaign | Campaign ID and Lead ID | Every other field optional. The Lead ID has to come from a lookup, because it is Smartlead's identifier and not a Clay row ID. |
| Update lead category | Campaign ID, Lead ID and Category ID | The category list is a dropdown populated from your Smartlead account, so categories are defined there rather than typed here. |
| Remove lead from campaign | Campaign ID and Lead ID | Returns Ok as true when the lead was removed. The only action on this integration that returns a usable boolean. |
| Custom fields | Key-value pairs on the add and update actions | The field name on the left and the value on the right. This is how a Clay-written personalisation line reaches the campaign as a merge variable. |
| Anything about replies | Not an action | Smartlead publishes webhooks for email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated, and consuming them is a job for a server rather than for a Clay column. |

### The two duplicate switches, and which way they point by default

| The action | How it reads on the record |
|---|---|
| Allow Duplicate Leads Across Campaigns | Off by default. A lead already in another Smartlead campaign is not added |
| The same switch, turned on | The lead can sit in several campaigns, but still only once per individual campaign |
| Allow Leads from Community Bounce List | On by default. Leads on Smartlead's shared bounce list are added anyway |
| The same switch, turned off | Leads found on that list are skipped, which Clay notes is not the recommended default |
| A lead with no Lead ID in your table | Update, Update category and Remove will not run. Lookup first |

**What does not cross:**

- Campaign creation. Clay states that all Smartlead actions require an existing campaign and that campaigns cannot be created from Clay, so the campaign is always built in Smartlead first.
- Replies, opens, clicks and bounces. The status action returns steps and sends; everything else is a Smartlead webhook rather than a column.
- A Clay row ID used as a Lead ID. Clay calls this out as its own troubleshooting entry, because the two look interchangeable and are not.

## Connect it, in this order

**Who has to do it:** Whoever owns the Clay workbook, plus somebody who can generate a Smartlead API key. No admin on either side.
**How long:** Ten minutes, once the Smartlead campaign exists. Building the campaign is the longer half.

### 1. Check the Clay plan first

*Where:* Clay: pricing

Clay's integration catalogue puts Smartlead at Included in Launch+, so the Free plan does not carry it. That is a gentler gate than the CRM integrations, which start on Growth, and it still means a workspace on Free cannot run this at all.

### 2. Build the campaign in Smartlead before you open Clay

*Where:* Smartlead: Campaigns

Clay states it plainly: all Smartlead actions require an existing campaign, and campaigns cannot be created from within Clay. Every action takes a Campaign ID from a dropdown populated by your account, so an empty Smartlead means an empty dropdown.

### 3. Generate the API key and paste it into Clay

*Where:* Smartlead: app.smartlead.ai/app/settings/profile

Add enrichment, search Smartlead, then + Add account and enter the key. This is an API key rather than OAuth, so it carries whatever the key carries and it is revoked in Smartlead rather than disconnected in Clay.

### 4. Qualify in the table before anything is pushed

*Where:* Clay: run settings, Only run if

Clay's own best practice for this integration is to enrich and score first and push only what passes. The action costs the same whether the lead was worth sending to or not, so the condition on the column is where the money is saved.

### 5. Decide the two duplicate switches deliberately

*Where:* Clay: Add lead to campaign

Allow Duplicate Leads Across Campaigns is off by default, so a lead already in another Smartlead campaign is not added. Allow Leads from Community Bounce List is on by default, so leads on Smartlead's shared bounce list are added unless you turn it off.

### 6. Run a lookup before any update or removal

*Where:* Clay: Lookup lead in campaign

Update, Update category and Remove all need Smartlead's internal Lead ID, which is not a Clay row ID. Lookup takes an email and returns the Id, so it is the column the other three read from.

### 7. Use the status action to close the loop you can close

*Where:* Clay: Lookup lead status in campaign

It returns the number of campaign steps, the number of emails sent so far and a status such as IN_PROGRESS. That is not reply data, and it is the only visibility into the campaign that comes back to the table.

### 8. Turn on Auto-update once the conditions are right

*Where:* Clay: run settings

Clay recommends it for trigger-based workflows so new rows push automatically. Turn it on after the filters are correct rather than before, because a row added by mistake is an action spent and a lead sent.

The order is almost entirely about not pushing the wrong person: three of the eight steps are filters rather than configuration. That is the discipline every pair on the [orchestration layer](layer:orchestrate) needs, and it is sharper here because the output is an email somebody receives rather than a field somebody reads.

## How to check it worked

- Push one lead and confirm it appears in the Smartlead campaign. The action reports success and returns no fields, so the campaign is the only confirmation there is.
- Push a lead you know is already in a different campaign with the duplicate switch off. It should not be added, and seeing that once is cheaper than wondering why a batch came up short.
- Run Lookup lead in campaign on that lead and read Lead Campaign Data, which lists every campaign it is enrolled in. That is the field that tells you whether your table is competing with another campaign.
- Check Is Unsubscribed on a few rows before a bulk push. It comes back on the lookup and it is the one piece of suppression data this integration can see.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Leads are not being added to the campaign | Clay's first documented troubleshooting entry: all Smartlead actions need a campaign that exists and is active in Smartlead. | Confirm the campaign before re-running. The Campaign ID dropdown is populated from your account, so a campaign that is missing there is missing in Smartlead rather than in Clay. |
| Some leads were skipped and they are all in other campaigns | Smartlead will not add a lead that already exists in a different campaign, which is the default and is a deliverability protection rather than a fault. | Turn on Allow Duplicate Leads Across Campaigns only when you intend somebody to be in two sequences. A lead can still only be added once per individual campaign either way. |
| Update or Remove will not run | They need Smartlead's internal Lead ID, and a Clay row ID is not it. Clay documents this as its own troubleshooting entry because the two are easy to confuse. | Run Lookup lead in campaign first and map its Id output into the Lead ID field. The same applies to Update lead category. |
| Bounced addresses are reaching the campaign | Allow Leads from Community Bounce List is on by default, so leads on Smartlead's shared list are added unless you switch it off. | Turn it off for a cold list. Clay recommends leaving it on for most use cases, which is a judgement about your list rather than about the setting. |
| The personalisation column did not reach the campaign | Anything beyond the named fields has to be sent as a custom field key-value pair, and the key has to match the merge variable in the Smartlead sequence. | Add it under Custom Fields on the add or update action, with the field name exactly as the campaign expects it. |
| A push succeeded and you cannot tell what it did | Add lead to campaign and Update lead in campaign both confirm success and return no output fields, by design. | Follow with Lookup lead in campaign if you need proof in the table. Remove is the one action that returns a usable value, Ok set to true. |
| The table pushed rows you were still working on | Auto-update was on while the filters were still being built, so rows added to the table went straight out. | Turn auto-update on last, and pair it with Only run if. Clay recommends auto-update for trigger-based workflows, which assumes the conditions are already right. |
| Nothing about replies is coming back | There is no reply action. Smartlead delivers engagement over webhooks for email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated. | Point those at a server rather than at Clay. Smartlead retries failed deliveries, marks an event failed after three attempts, and has a Retrigger Webhooks endpoint for the ones that failed. |

## What breaks, from the vendors' own docs

- **No campaign creation, by design.** Clay states that all Smartlead actions require an existing campaign and that campaigns cannot be created from Clay. The campaign dropdown reads from your Smartlead account, so a table is always pointed at something somebody built elsewhere, and a campaign that is renamed or deleted breaks the column rather than failing loudly.
- **An API key held in another product.** Authentication is a Smartlead API key from your profile settings, pasted into Clay. It is long-lived, it is revocable only in Smartlead, and rotating it breaks every table that uses it simultaneously. Keep a note of which tables hold it, which is advice nobody follows until the first rotation.
- **Engagement does not come back.** Replies, bounces, opens and unsubscribes are not returned to the table. Smartlead exposes them through webhooks to an endpoint you control, scoped by user, client or campaign, so the loop closes through infrastructure you build rather than through Clay. Plan that if suppression on engagement matters.
- **The expensive part is above the action.** Pushing, updating and removing are cheap. The waterfall that decided whether a lead qualified is where the credits go. Use the conditional run setting so the enrichment stops on rows that already failed a cheaper test, and test on ten rows before five hundred.

## The APIs, if you are building around it instead

### Clay

- **Base:** `Configured in the table, not through an API`
- **Auth:** Per-integration, set in the workbook.

| Call | Request | What it does |
|---|---|---|
| `ACTION HubSpot / Salesforce Lookup` | - | Read-only. Pulls records into the table and changes nothing in the CRM. |
| `COLUMN HTTP API` | `POST https://api.reversecontact.com/v2/enrich/persons\nHeaders: { "Authorization": "Bearer rc_...", "Content-Type": "application/json" }\nBody: { "email": "/Work Email" }` | `/Work Email` is a column reference, so each row posts its own value. This is how a provider with no native listing becomes a column. |
| `ACTION HubSpot / Salesforce Update` | - | Writes back. Immediately live to every CRM user. Turn on "ignore blank values" and exclude rep-owned properties. |

**Rules that will cost you time if you skip them:**

- **Clay bills per action on the attempt, not the result.** Effective cost per filled field is the action rate divided by your match rate. Order a waterfall cheapest-first and use conditional runs so the expensive source only sees the residue.
- Import a filtered slice, never the whole portal. Filter on the gap you are filling.
- Run read-only until the columns look right, write to ten rows, open them in the CRM, and only then schedule.

Docs: https://university.clay.com/docs/hubspot-integration-overview

### Smartlead

- **Base:** `https://server.smartlead.ai/api/v1`
- **Auth:** API key as a query parameter.

| Call | Request | What it does |
|---|---|---|
| `POST /campaigns/{id}/leads` | `{ "lead_list": [ { "email": "...", "custom_fields": {...} } ] }` | Push the survivors of your suppression rules into a campaign. |

**Rules that will cost you time if you skip them:**

- Webhooks fire on every send, reply, bounce and unsubscribe. Route replies to a human within minutes; send the rest to a report.
- Entry pricing comes off a plan slider. Confirm the tier against your own mailbox count rather than budgeting from the headline.

Docs: https://api.smartlead.ai/reference

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Clay docs: Smartlead integration: https://university.clay.com/docs/smartlead-integration-overview
- Clay integrations: Smartlead.ai: https://www.clay.com/integrations/data-provider/smartlead-ai
- Clay pricing: the plan comparison: https://www.clay.com/pricing
- Smartlead API: webhook integration guide: https://api.smartlead.ai/guides/webhook-integration
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-smartlead-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-smartlead-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
