Push, look up, update and remove, on a campaign Clay cannot create.
Clay Launch or above, a Smartlead API key, and a campaign that already exists
Contacts, Lists, one way, out.
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.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| 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 | Event only | Not created from Clay. Every action requires an existing Smartlead campaign. |
| Replies, bounces and opens | Event only | Not returned to the table. Smartlead's webhooks post those to an endpoint you control instead. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
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. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| 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 |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, five action rows and three documented exclusions, each one's note, and the four vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The lookup is the hinge of the whole integration: four of the six actions cannot run without what it returns. Building the table with the lookup column second, immediately after the email, is what makes the rest of it composable rather than a sequence of dead ends.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| 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 |
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.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
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.
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.
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.
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.
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.
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.
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.
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 needs, and it is sharper here because the output is an email somebody receives rather than a field somebody reads.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/clay-smartlead/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-smartlead.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyClay'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.
WhySmartlead 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.
WhyThey 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.
WhyAllow 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.
WhyAnything 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.
WhyAdd 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.
WhyAuto-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.
WhyThere 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.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
It's not a sequencing tool. It's a tool that takes different parts of the outbound process (list build, enrichment, research, AI personalization, etc.) and pulls it all into one place. Because of how flexible this model is, you can create very customized flows to fit what you're looking for.
r/Entrepreneur·June 2024·2 points
From somebody running a Clay consultancy, so read the enthusiasm accordingly, and the definition is the right one. It also explains the shape of this integration: six actions that manage a lead inside somebody else's campaign, and none that create a campaign.
At my last shop we ran the full modular stack. Apollo for data. Clay for enrichment. Smartlead for sending. Aircall for calls. HubSpot for CRM. Bombora for intent. Six tools. Total cost was around $1,400/month. We had a dedicated ops person spending roughly 15 hours a week keeping
r/microsaas·April 2026·1 points
From somebody describing five years running outbound ops for agencies, and the quote is cut where the cached comment is. The fifteen hours is the number worth arguing with internally: this integration exists to remove the CSV step from exactly that job, and it removes one of the six tools' worth of glue rather than the glue itself.
Use LemList for multi-channel outbound sequences across email, Linkedin, and phone call. You can connect 5x mailboxes per user = 150/user/day and 20-25 connection requests per day. You can use the hubspot integration to sync lead activity, replies, and meetings booked.
r/revops·December 2025·4 points
About a competing sender rather than Smartlead, and it transfers: the constraint on an outbound programme is mailboxes and daily sends, not how fast a table can push. A Clay table that can enrich ten thousand rows is feeding a channel measured in a few hundred a day.
They also have a good database of prospects that you can access for free (they call it "Find People"). The drawbacks is that It only contains publicly available linkedin profiles and data can be outdated as they refresh it every 30/45 days.
r/Emailmarketing·May 2024·2 points
The refresh window is this person's figure rather than a published one, so treat it as a reason to verify rather than as a number. The point that survives is that what you push into a campaign is only as fresh as the provider it came from, and the push action cannot tell the difference.
Clay is an overly complicated and expensive workflow tool. It pulls data from all these different sources into one spot, but you're really paying a premium for that. Honestly, you can find cheaper, more specialized tools for whatever you're trying to do.
r/Emailmarketing·November 2024·10 points
The highest-scoring comment in the set and a fair challenge. The answer this pair gives is the conditional column: a cheaper specialised tool will push a list, and what Clay adds is deciding per row whether the push should happen at all. If nobody is going to write that condition, the complaint is correct.
Nobody discusses this pair by name, so the search was for the job instead: building a list in one tool and sending from another. What comes back is an argument about whether the modular stack is worth its overhead, and the most useful contributions are from people who have run it and costed it. The recurring correction is that Clay is not a sequencer and was never meant to be, which is exactly why this integration exists and exactly what people keep having to explain.
This is a job search rather than a pair search, and it shows: none of the five is about the integration working or failing. They are about whether the two-tool arrangement is worth running, which is the decision in front of anybody reading this page, and the documented behaviour above is what the arrangement actually costs to operate.
The removal action is what separates this from the other sending integrations on the hub and it is the one most teams never configure. Outbound lists go stale in predictable ways: somebody changes job, a company gets acquired, a domain turns out to belong to a competitor or an existing customer. All of that arrives as an enrichment result in a table, and with a removal action the same pass that discovers it can act on it. Without one, the discovery becomes a report that somebody is meant to work through in the sending tool, and in practice does not.
What the pair does not give you is the other half of suppression, which is engagement. A lead who replied, bounced or unsubscribed is known to Smartlead and invisible to Clay. Smartlead's webhooks will post those events to an endpoint you control, with HTTPS required and a signature header, and that is the sanctioned route. It is an afternoon of work in whatever is already receiving webhooks for you, and it is the difference between a list that improves and one that only grows.
Underneath all three Clay sending pairs is the same division of labour, and it is worth making explicit because it decides where a problem belongs.
When those three are clear, the integrations between them are small and boring, which is the goal. When they are not, teams try to make one tool do all three and the orchestration layer fills up with workarounds.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Clay, Smartlead and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Push enriched leads into an existing campaign, look up and update lead details, manage campaign status and remove leads, all as enrichment columns on a table. Clay names the common patterns itself: outbound prospecting, where the list is built and enriched before anything is sent; lead qualification, where enrichment scores and filters before a lead enters a sequence; and campaign management, where statuses are read and unqualified leads removed without opening Smartlead.
No. Clay is explicit that every Smartlead action requires an existing campaign and that campaigns cannot be created from within Clay. The campaign id appears as a dropdown populated from your Smartlead account, so the sequence, the mailboxes and the schedule are Smartlead decisions taken before the table runs.
With a Smartlead API key, found in your Smartlead settings under your profile, pasted into Clay when you add the account. Like the other sending tools on this hub it is a long-lived credential held in another product rather than an OAuth connection, so rotating it affects every table using it.
Because the table is where the disqualifying information usually arrives. An enrichment that comes back with the wrong headcount, a competitor domain or a job change can trigger a removal in the same pass that discovered it, rather than producing a list somebody is supposed to action in Smartlead later. That is the part of this integration that most teams underuse.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.