Clay and Outreach

Four actions, and the one that matters adds an enriched row to a sequence.

What you have to buy first

Clay Launch or above, an Outreach contract, and twelve read-write scopes you cannot refuse

What moves

Contacts, Lists, one way, out.

A deliberately small integration that closes the most useful loop in outbound: a Clay table builds and enriches the row, scores it, writes the personalisation, and then pushes it straight into an Outreach sequence without a CSV ever existing. Four actions cover it, create, update, look up and add to sequence, and all four are added as enrichment columns rather than configured in a settings screen. What it is not is a sync. Nothing comes back from Outreach, so reply and meeting data lives there and the table is a one-way feed.

What actually syncs

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.

WhatDirectionWhat that means in practice
New prospects One way, out Create prospect, taking email plus optional name, company, title, address, contact preferences, social links and campaign fields.
Existing prospects One way, out Update prospect, keyed on id or email, across the same field set.
Sequence enrolment One way, out Add to sequence, which is the action most tables are built to reach. Mailbox ids are looked up with their own action.
Prospect lookups One way, in Look up prospect by email or id, optionally including the sequences they are already in, which is how a table avoids re-enrolling somebody.
Personalised copy One way, out Email templates on the table send with custom field inputs, so the column that wrote the line is the thing that delivers it.
Replies, opens and meetings Event only Nothing comes back. Outreach is where performance lives and the table never learns what happened.

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.

Which field lands where

Five actions and a permission grant that is wider than all five. The actions themselves are narrow and well behaved; the scopes they ask for are not, and both facts belong on the same page.

In ClayIn OutreachWhat to know about the match
Lookup prospect Email or prospect ID, both optional Include Sequences is the input worth setting: it returns what the person is already enrolled in, which is the only duplicate protection on this pair.
Create prospect Email, everything else optional Optional groups cover basics, address, contact preferences, social and websites, additional phone numbers, campaign and source fields like tags and event name, and personal details.
Update prospect ID and email The same optional groups as Create. The ID is required, so this action lives downstream of a lookup.
Add to sequence Prospect ID, Sequence ID and Mailbox ID All three required, and the sequence must be Active in Outreach. This is the action the integration exists for and the one with the most prerequisites.
Lookup mailbox by email address An email address Exists only to supply the third required input above. Its presence in a five-action integration tells you how often that input is the blocker.
Email templates Columns on the table, sent with Create prospect Clay documents adding templates to the table and sending them with custom field inputs, which is how the personalisation written in Clay reaches the first touch.
Replies, opens, meetings Nothing comes back There is no read action for engagement. Outreach holds performance and the table holds the list, and joining them is a job for the CRM both write to.
Sequence creation Not an action Like every sequencer pair on the Clay hub, the campaign is built in the sending tool first and Clay only populates it.

The twelve scopes Clay requires, none of which can be switched off

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 actionHow it reads on the record
prospects.all, recipients.allRead and write every prospect and recipient. Expected, and the reason the integration exists
sequences.all, sequenceSteps.all, sequenceStates.allRead and write every sequence, its steps and every prospect's state in it
mailboxes.allRead and write every mailbox, which is what makes the mailbox lookup possible
opportunities.all, opportunityStages.allRead and write every opportunity and stage, none of which any of the five actions touches
users.all, roles.allRead and write every user and role in the Outreach org
stages.all, events.allRead and write every prospect stage and every event

What does not cross

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.

  • Any way to refuse a scope. Clay describes these as permissions that cannot be disabled and are always requested, which is unusual: its HubSpot integration makes most scopes optional and ships three of them switched off.
  • A sequence that is paused. Clay states sequences must be Active for a lead to be added successfully.
  • Anything coming back from Outreach. The integration is a feed in one direction, so reply handling and meeting booking stay where they happen.

Every row above travels as a file: eight field mappings, six 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.

Field map

Read the two tables against each other and the asymmetry is the story: five actions that touch prospects and sequences, against twelve scopes that include opportunities, users and roles. Nothing suggests Clay uses the extra reach, and an Outreach admin is entitled to ask why it is being granted before the connect button is pressed.

Which Clay plan reaches which kind of tool

Clay bands every integration by plan rather than pricing them individually, and the bands run in an order worth knowing before you evaluate a chain: 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 planData providers, like ApolloSequencers: Outreach, Smartlead, lemlistCRMs: HubSpot, Salesforce
Free Included Not included Not included
Launch Included Included Not included
Growth Included Included Included
Enterprise Included Included Included
Included
Read off Clay's own catalogue, which states a plan band per integration: Apollo is Included in All Plans, Outreach, Smartlead and lemlist are all Included in Launch+, and the pricing page marks CRM integrations as included from Growth.
Not included
Not available on that plan at any volume. Every action on all four is additionally marked Bring Your Own Account Required, so your own contract with the other vendor is a separate prerequisite.

Counted off that grid, of twelve pairings: nine give you included, three give you not included. Outreach is in the middle column, so the Clay gate here is the mild one. The gate that should slow you down on this pair is not a plan at all, it is the scope list above, and it applies identically on every Clay tier.

How to connect Clay to Outreach

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.

Who has to do it
Whoever owns the Clay workbook, and somebody willing to grant Outreach scopes across the whole org. In a governed Outreach instance that is a conversation, not a click.
How long it takes
Ten minutes. The scope review is the part that should take longer.
Setup checklist 0 of 8 done

Clay: the consent screen

Clay lists them as permissions that cannot be disabled and are always requested: users, stages, sequenceSteps, sequenceStates, sequences, roles, recipients, prospects, opportunityStages, opportunities, mailboxes and events. Every one is the .all variant, meaning read and write.

Clay: pricing

Clay's catalogue puts Outreach at Included in Launch+, so the Free plan does not reach it. Every action is also marked Bring Your Own Account Required, which here means your own Outreach contract rather than anything Clay resells.

Clay: Add enrichment, Outreach

Search Outreach, pick one of the actions under Integrations, then Select Outreach account or + Add account to authenticate. The connection is made where the column is built rather than in a workspace settings screen.

Outreach: Sequences

Clay notes it on the action itself: sequences must be Active in Outreach for a lead to be added successfully. A paused sequence takes the call and does not enrol anybody.

Clay: Lookup mailbox by email address

Add to sequence requires a Mailbox ID alongside the prospect and sequence, and that action exists purely to turn a sending address into one. Resolve it once rather than per row.

Clay: Lookup prospect

It takes an email or a prospect ID, both optional, and has an Include Sequences switch that tells you what the person is already enrolled in. That switch is the one thing standing between your table and double-enrolling somebody.

Clay: Create prospect, Update prospect

Create takes an email plus optional basics, address, contact preferences, social links, extra phone numbers, campaign and source fields, and personal details. Update takes the same plus an ID. Neither enrols anybody; Add to sequence is its own action.

Clay: run settings, Only run if

The expensive columns are upstream and the irreversible one is downstream. Gating the enrolment on the score keeps the research you paid for and stops the email you would regret.

Seven of these eight steps are ordinary, and the first one is not: this is the broadest permission grant any pair in this directory asks for, and it is presented as a connect button. The Outreach and Salesforce pairing shows what Outreach's own permission model looks like when somebody has thought about it.

Hand it to an agent instead

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-outreach/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-outreach.md

What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

It is a feed, not a sync
Clay writes to Outreach and reads only what you explicitly look up. No reply, open, bounce or meeting data returns to the table, so a Clay table cannot suppress on engagement unless you build the lookup yourself. Any reporting that spans list quality and sequence performance has to happen somewhere both tools write, which usually means the CRM.
Check before you enrol, or you will double-enrol
The lookup action can include the sequences a prospect is already in, and it exists because the create and add-to-sequence actions will happily act again on somebody already being sequenced. A table that pushes without that check produces the duplicate-outreach problem the integration is supposed to prevent.
Credits are spent above the action, not on it
Pushing to Outreach is cheap; filling the row is not. A waterfall that tries several providers for an email and a phone number is where a Clay bill comes from, so test on ten rows before running five hundred and decide what a row is worth before you decide what a sequence is worth.
Authentication is per table, not per workspace
The Outreach account is selected inside the enrichment modal, so different tables can point at different Outreach accounts and nothing warns you that they do. In a team running several tables that is a real source of prospects landing in the wrong place, and it is worth a naming convention rather than a discovery in week three.

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.

The 8 failures people actually hit

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.

01

The lead was not added to the sequence

WhyThe sequence is not Active in Outreach. Clay states this requirement on the Add to sequence action itself.

Activate the sequence, then re-run the column. A paused sequence is the most common cause and it produces no obvious error on the Clay side.

02

Add to sequence will not run at all

WhyIt needs three inputs and most tables only have two. Prospect ID, Sequence ID and Mailbox ID are all required.

Run Lookup mailbox by email address once to resolve the mailbox, and carry the prospect ID forward from Create or Lookup prospect.

03

The same person was enrolled twice

WhyNothing in the push checks existing enrolment unless you ask. Lookup prospect has an Include Sequences switch and it is not on by default.

Add a lookup column with Include Sequences on, and gate the enrolment column on what it returns. There is no de-duplication setting to turn on instead.

04

Update prospect is failing on rows that have an email

WhyUpdate requires the ID as well as the email. An email alone is enough for Create and not for Update.

Look the prospect up first and map its ID into the Update column. This is the same lookup-before-write shape every Clay sequencer pair needs.

05

Emails went out from the wrong address

WhyAdd to sequence sends from whatever mailbox the Mailbox ID names, and a single hard-coded ID applies to every row.

Resolve the mailbox per owner rather than once for the table if reps send from their own addresses. The lookup action takes an email, so the owner column can drive it.

06

An Outreach admin is asking why Clay can see opportunities

WhyBecause it can. opportunities.all and opportunityStages.all are in the required scope list, alongside users.all and roles.all, and Clay documents all twelve as not disableable.

There is no configuration answer. Either the grant is acceptable or the integration is not, and that is a decision to take before connecting rather than after.

07

Nothing is coming back from Outreach

WhyBy design. The five actions write and look up; there is no engagement read.

Read performance in Outreach, and join it to the list in whichever CRM both tools already write to.

08

Credits went on rows that were never enrolled

WhyThe enrichment columns upstream run before the enrolment column decides anything, and each one spends an Action per record.

Move the qualifying condition as far up the table as it will go. Clay bills per record enriched regardless of what happens downstream.

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.

When this is the right integration

Set it up when

  • A list has to arrive in a sequence already enriched and personalised
  • Scoring should decide who gets sequenced and who does not
  • You are tired of exporting a CSV and re-importing it

Do not bother when

  • You need engagement data back in the table to suppress on
  • The list is static and a one-off import would do
  • Nobody has decided what makes a row worth sequencing

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.

What practitioners say about it

Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2023 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.

The correction people keep having to make

lol yeah Clay isn't for prospecting it's for scraping and pulling info like contact data or LinkedIn data. Think of it as a data enrichment tool that is a part of your overall cold outreach stack.

r/sales·June 2024·3 points

Answering somebody asking what Clay adds over Apollo or Lusha. Part of a stack is the operative phrase, and five actions that manage a prospect inside somebody else's sequence is what being part of a stack looks like in practice.

Clay was not a sequencer, and now partly is

clay isn't even really a sequencer, I think they are rolling out some functionality there but I haven't seen anything amazing, yet.

r/gtmengineering·September 2025·2 points

Worth printing because it has dated itself usefully. Clay's pricing page now sells domains and mailboxes for a Clay Sequencer, so the functionality arrived. It does not make this integration redundant: a team that already runs Outreach is not moving its sequences, and this pair is for that team.

The price objection, stated at its strongest

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 the honest answer is that it depends entirely on whether anybody writes the conditions. A table that pushes everything into a sequence is an expensive CSV. A table that decides per row which prospects deserve a sequence slot is the thing being paid for.

What the sequencing side is actually constrained by

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.

r/revops·December 2025·4 points

About a different sequencer, and the shape of the constraint is the same one Outreach lives under: mailboxes and daily sends. A table that can enrich ten thousand rows is feeding a channel measured in hundreds a day, which is the real argument for putting the filter in Clay.

The spaghetti complaint, which this integration is a response to

It's a big spaghetti junction of other peoples tools connected together in the false hope it'll help prospecting.

r/sales·October 2024·23 points

Hostile and not wrong about the failure mode. The counter is that a native integration with five documented actions is the opposite of spaghetti; what makes a stack spaghetti is the CSV between the tools, which is exactly the step this pair removes.

What the threads add up to

The pair by name returns nothing, so this is a search for the job: using a table to build and enrich a list that something else sends. The threads are an argument about whether Clay earns its price, and the useful part is that both sides agree on the division of labour. Clay is not a sequencer, people say so repeatedly and sometimes irritably, and the integration on this page is the seam that creates. One comment from 2025 says Clay was starting to roll out sequencing of its own, which has since shipped as the Clay Sequencer and does not change what this pair is for.

A job search returns opinions about the arrangement rather than reports of the integration failing, which is the honest outcome for a pair nobody names. The one checkable claim, that Clay had no sequencer, is now out of date, and saying so is more useful than leaving the quote out.

The longer answer

The reason to run this rather than an export is that the decision and the delivery end up in the same place. In a CSV workflow, the table decides who is worth contacting and a human carries that decision across to the sequencing tool, where it is re-interpreted. With the action in the table, the row that passed the score is the row that got enrolled, and the personalisation computed in a column is the copy that went out. That is a shorter distance between the thinking and the sending, and it is most of the value.

What to design carefully is the suppression side, because the integration gives you half of it. The lookup action tells you which sequences a prospect is already in, and nothing tells you what happened in them, so the table knows about overlap and not about outcomes. Most teams solve this by making the CRM the arbiter: Outreach writes activity there, the table reads from there, and the loop closes outside Clay. That is the shape the outbound list build uses.

The broader point is that Clay is behaving as the orchestration layer rather than as a data vendor here. It is not providing the prospect, it is deciding which prospects exist and what is known about them before anything is sent, then handing them to the tool that sends. Every pair on this hub has that shape, and it is why a Clay table ends up as the place a go-to-market process is actually written down.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-11
Sources
4 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

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, Outreach 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.

Clay and Outreach, asked and answered

What can Clay do with Outreach?

Four actions, added to a table as enrichments: create a prospect, update a prospect, look up a prospect, and add a prospect to a sequence. There is a fifth that exists only to make the fourth work, finding mailbox ids. Together they turn a Clay table into the thing that fills Outreach, which is the whole point: the row arrives enriched, scored and personalised rather than as a name and an email.

How do I connect it?

From inside a table. Click Add enrichment, search for Outreach, pick the action, and the modal asks you to select an Outreach account or add one through authentication. There is no separate integrations screen to configure first, which is the pattern for every Clay integration and surprises people who expect an admin step.

Can I send personalised copy from Clay?

Yes, and it is the reason to do this in Clay rather than through a CSV. Clay documents adding email templates to the table and sending them with custom field inputs on the create-prospect action, so the personalisation computed in a column travels with the prospect instead of being pasted into a sequence later. That is a different workflow from importing a list and then writing copy.

What does it cost?

Clay credits for the enrichment columns that fill the row, and nothing extra for the push itself beyond your Outreach contract. The expensive part of any Clay table is the waterfall above the action, not the action, so model the cost per enriched row rather than per prospect pushed.

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.

Ask an assistant