Three actions, an API key, and a campaign that has to exist first.
Clay Launch or above, a lemlist API key, and a campaign that already exists
Contacts, Lists, one way, out.
A small, well-scoped integration that does the one thing a CSV cannot: it carries the thinking with the lead. Three actions, add, update and look up, each keyed on a campaign that already exists in lemlist, with the personalisation written in a Clay column delivered as part of the push. The conditional run setting is the part worth using properly, because it turns the table into the thing that decides who is worth a campaign slot rather than a list that fills one. What it is not is a sync: nothing comes back, so engagement lives in lemlist.
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, taking a campaign id plus email, LinkedIn URL, name, phone number and the rest of your mapped fields. |
| Existing leads | One way, out | Update lead in campaign, keyed on the email address or the lead id, across the same field set. |
| Duplicate checks | One way, in | Look up lead in campaign by email, which is how a table avoids adding somebody who is already being sequenced. |
| Personalised copy | One way, out | Per-lead data including the email copy written in a Clay column, so the personalisation is part of the lead rather than a later edit. |
| Campaigns themselves | Event only | Not created from Clay. The campaign, its steps, its schedule and its sending identities are all set up in lemlist first. |
| Replies, opens and bookings | Event only | Nothing returns to the table. lemlist is where performance lives, and its [HubSpot integration](pair:hubspot+lemlist) is how that reaches a CRM. |
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.
Clay exposes three actions. What they do once the request reaches lemlist is documented on lemlist's side rather than Clay's, and two of those behaviours decide how you build the table.
| In Clay | In lemlist | What to know about the match |
|---|---|---|
| Add Lead to Campaign | Campaign ID required, the rest optional | Email, LinkedIn URL, name, phone and more. lemlist documents the underlying endpoint as creating and never updating, so this is not an upsert however it is used. |
| Update Lead in Campaign | Campaign ID, plus email or lead ID | The action for changing an existing lead. Pairing it with the lookup is what turns the two into the upsert that the add action is not. |
| Lookup Lead in Campaign | Email address or lead ID | Checks whether the lead exists in a campaign. The cheapest column on the table and the one that makes the other two safe. |
| Company fields | The shared company record | companyName, companyDomain, companyIndustry and any company-prefixed key reach the company the lead is matched to, which every other lead linked to it reads. Not scoped to the lead. |
| Any other key you send | A custom variable on the lead | Usable in the campaign as a merge tag. Letters, digits, underscore, hyphen, space and hash are kept; every other character becomes an underscore, and values are stored as text. |
| The API key | HTTP Basic, empty username | lemlist uses Basic rather than Bearer, with the key as the password and a leading colon before it. Clay handles the encoding; what it means for you is that the key is a credential, not a token with scopes. |
| Campaign creation | Not an action | The campaign has to exist in lemlist first. lemlist's own API can create one, but Clay does not expose that. |
| Replies, opens, meetings | Nothing comes back | There is no read action for engagement, so performance lives in lemlist and the table is a feed. |
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 |
|---|---|
| The contact already has a lead in this campaign | 400 LEAD_ALREADY_IN_CAMPAIGN, and nothing is written |
| The contact has a lead in a different campaign, with deduplicate on | 409 LEAD_ALREADY_IN_OTHER_CAMPAIGN |
| The campaign's own remove duplicates setting | Does not drive that check. Only the deduplicate parameter does |
| The contact and company behind the lead | Updated with the fields you sent, even though the lead was refused |
| updateStrategy left at its default | overwrite: sent values replace stored ones, and an empty value clears the stored one |
| updateStrategy set to fillEmptyOnly | Only empty fields are filled, and kept values are listed back as FIELDS_KEPT warnings |
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, six action rows and three documented exclusions, each one's note, and the five 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 second table is the reason this page cites lemlist's API documentation as well as Clay's: a refused lead that still rewrote its contact and its company is not a failure anybody would infer from a red cell in a table. Build the lookup column first and most of it stops mattering.
Clay sorts integrations into plan bands rather than pricing them one by one, and the order catches people out: 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: lemlist, Smartlead, 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. lemlist sits in the middle column, so the Clay gate is the mild one and Launch covers it. The number more likely to shape this pair is on lemlist's side: 20 requests per 2 seconds per API key, which is the ceiling a bulk push runs into long before any plan does.
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 catalogue puts lemlist at Included in Launch+, so a Free workspace cannot run it. Every action is also marked Bring Your Own Account Required, which here means your own lemlist subscription.
lemlist: Campaigns
Clay states the requirement directly: you must already have a campaign set up in lemlist to use this integration. All three actions take a Campaign ID, and there is no create-campaign action.
lemlist: Settings, Integrations
Profile picture, Settings, the Integrations tab, Generate a new API key. lemlist warns that you will not be able to see it again, so it goes into Clay or a password manager in the same minute it is created.
Clay: Add enrichment, lemlist
Search lemlist, pick an action under Integrations, then + Add account and paste the key. Note what this key is: lemlist authenticates with HTTP Basic using an empty username and the key as the password, so it is a password in the literal sense.
Clay: Lookup Lead in Campaign
It checks whether a lead exists in a campaign by email or lead ID. The add action creates and never updates, so without this column the table has no way to tell a new lead from one it is about to be refused for.
Clay: the mapped columns
Company name, company domain, company industry and any company-prefixed key reach the shared company record the lead is matched to, not that lead alone. Every other lead linked to the same company reads what you wrote.
Clay: additional fields
Any extra key-value pair you send is stored as a custom variable usable in the campaign as a merge tag. Only letters, digits, underscore, hyphen, space and hash survive; anything else, a full stop or a dollar sign, is replaced with an underscore.
Clay: run settings, Only run if
All three actions take Auto-update and Only run if. The add is the one that cannot be undone from the table, so that is the column the score belongs on.
Three actions is the smallest sequencer integration on the Clay hub, and the brevity hides two behaviours that are not small: an add that refuses rather than updates, and company fields that write to a record shared across leads. Both are in lemlist's API documentation rather than in Clay's, which is why this page cites both.
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-lemlist/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-lemlist.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.
WhyThe contact already has a lead in that campaign. lemlist documents the add endpoint as one that creates and never updates, so this is the designed response rather than a fault.
Use the Update Lead in Campaign action for anybody already there, gated on a lookup column. Nothing was written by the refused call.
WhyDeduplication is on and the contact has a lead in a different campaign.
Decide whether somebody in another campaign should be enrolled again. Note that only the deduplicate parameter drives this check: the campaign's own remove duplicates setting does not.
WhyThe lead is always new, and the contact and company it matches are updated with whatever fields you sent regardless.
Treat the add action as a write to the contact even when it fails as a lead. If that is not what you want, look up first and branch.
WhyupdateStrategy defaults to overwrite, where a sent value replaces the stored one and an empty value clears it.
Send overwriteIgnoreEmpty to keep stored values where your column is blank, or fillEmptyOnly to fill only what is empty. Kept values are reported back as FIELDS_KEPT warnings.
WhyThe custom variable name was rewritten on storage. Only letters, digits, underscore, hyphen, space and hash are kept, and anything else becomes an underscore.
Name the Clay column with characters lemlist keeps, and match the merge tag to the stored name rather than the one you typed.
WhyCompany-prefixed fields reach the company record the lead is matched to, which is shared by every lead linked to it.
Keep company columns out of a bulk push unless you intend to edit the company. lemlist has a separate Upsert Company endpoint for doing it deliberately.
Whylemlist rate-limits all routes at 20 requests per 2 seconds, per API key.
Read Retry-After and X-RateLimit-Remaining, which come back on every response. Note X-RateLimit-Reset is a human-readable date rather than a timestamp, which trips up anything parsing it.
Whylemlist shows it once at creation and never again.
Generate a new one in Settings, Integrations, and store it properly this time. Rotating it means re-entering it in Clay, since the connection is the key.
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.
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
The most concrete comment in the set, and the numbers are that person's rather than lemlist's published figures. The shape is what matters: a table that can enrich thousands of rows is feeding a channel measured in a few hundred sends a day, which is the argument for putting the qualifying filter in Clay rather than in the campaign.
We wanted to start using Lemlist and Clay for our outbound and were frustrated that neither integrated well with Attio's API.
r/CRMSoftware·January 2026·2 points
From somebody who moved through four CRMs in a few months. Clay and lemlist talking to each other is the easy half; what decides a stack is whether both can reach the system of record, and that is a question about the CRM rather than about this pair.
The Lemlist feedback loop is clutch, most outbound just disappears into the void.
r/SaaS·February 2026·2 points
Written about lemlist's own reporting rather than about Clay. It is here because the three actions on this page are all outbound: the feedback loop this person values happens in lemlist, and the table never sees it.
Like others have mentioned here, Clay is good but it is a complex tool. You'd probably have to end up paying an agency that specializes in Clay to help set things up effectively for you. You've also got to pay the subscriptions for the different tools that integrate with Clay.
r/salesdevelopment·August 2024·1 points
The second sentence is the one that applies here, and it is correct: Clay's catalogue marks every action on this integration Bring Your Own Account Required, so a lemlist subscription is a prerequisite rather than something Clay resells.
Clay gives access to more data providers (Storeleads, G2, Predictleads, Job openings data, Harmonic, HTTP requests...). They also have a good database of prospects that you can access for free (they call it "Find People").
r/Emailmarketing·May 2024·2 points
A comparison written by somebody selling an alternative, which is why only the uncontested half is quoted. The relevant point is that everything expensive about this table happens before the lemlist column, and the push itself is the cheapest thing on it.
The pair by name returns nothing, so the search was for the job: enriching in one tool and sending from another. Two things come out of it. The constraint on this arrangement is the sending side rather than the table, measured in mailboxes and daily sends. And the integration gap people actually complain about is the CRM at the other end, not the sequencer, which is worth knowing before anybody decides this pair is the missing piece.
None of the five describes this integration failing, which is what a job search returns for a pair nobody names. The documented behaviour above comes from lemlist's API reference instead, and it is more specific than anything in the threads: two error codes, a shared company record and a naming rule.
The reason this is worth more than an export is the same reason every Clay pairing on this hub is: the decision and the delivery stop being separate steps. A CSV workflow has the table decide who qualifies and a human carry that decision into the sending tool, where it gets re-interpreted and the personalisation gets rewritten. With the action in the table, the row that met the condition is the row that entered the campaign, carrying the line that was computed for it.
The constraint that shapes a build here is that lemlist owns the campaign. Clay cannot create one, so the shape of the outreach, how many steps, which mailboxes, what schedule, is decided elsewhere and the table fills it. That is a cleaner separation than it first appears, because it keeps sending policy with the sending tool, but it does mean a table and a campaign have to be designed together and a change to one can quietly invalidate the other.
Where the loop is incomplete is engagement, and the honest answer is to close it outside this pair. lemlist writes activity to HubSpot, where sent and replied become email objects and everything else becomes notes, which is covered on the lemlist and HubSpot page. Let the CRM be the arbiter of what happened, read from there if the table needs to know, and do not expect two tools that both write to a third to talk to each other directly.
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, lemlist 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.
Three actions: add a lead to a campaign, update a lead in a campaign, and look up whether a lead already exists in one by email. Each is added as an enrichment column on a Clay table, takes a campaign id, and carries the fields you map, including the email address, LinkedIn URL, name and phone number. The point is sending per-lead data from Clay, personalised email copy included, straight into a lemlist campaign.
With a lemlist API key rather than OAuth. In a Clay table click Add enrichment, search for lemlist, pick the action, then add the account and paste the key, which lemlist exposes under Settings and Integrations. That is a different trust model from the OAuth connections most pairs here use: the key sits in Clay and revoking it is a lemlist action.
Yes. Clay documents that you must already have a campaign set up in lemlist to use the integration, and every action takes a campaign id. Clay cannot create a campaign, so the sequence, the schedule and the sending identities are all decided in lemlist before a single row moves.
The personalisation travels with the lead. Clay sends per-lead data including the email copy written in a column, so the line computed from a company's recent news or a role change is attached to the lead rather than pasted in afterwards. The other half is conditionality: the enrichment only runs when the conditions you set are met, so the table decides who is worth a campaign slot.
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.