Clay integrations

Clay integrations, or how a tool with no app gets one

Ten integrations, and the reason Clay belongs in a directory like this: any HTTP API becomes a column, which makes it the shortest path between a data source and a CRM that has never heard of it.

clay.com 10 integrations
layerOrchestration, Data
entry$0/mo
authAPI key per workbook
automationAuto-update on a schedule, plus ...
verified2026-09-18
checked Guides written 10 of 10
10integrations checked
9built natively
4sync both ways
5need a plan upgrade
The short version

What decides a Clay integration

A table that reads your CRM, calls anything, and writes back.

Clay is the integration nobody lists as an integration. It reads records out of a CRM, runs them through whatever you point at, and writes the result back. The native providers are convenient; the HTTP column is the part that matters, because it means a tool with no marketplace listing anywhere is roughly as easy to wire in as one with a certified app.

What you are paying for is not the connection, it is the ability to change it. If your enrichment is one provider filling one field and that will still be true next year, a workflow webhook does the same job with no second meter. If the logic is conditional, changes monthly and is owned by someone who does not write code, the table is the entire point.

The economics are worth stating plainly. Clay bills per action rather than per result, so a lookup that finds nothing costs the same as one that succeeds. Your effective cost per filled field is the action rate divided by your match rate, which is why the ordering of a waterfall matters more than the choice of any single provider in it.

Clay sits in 2 of the seven layers this directory splits a stack into, the orchestration layer and the data layer among them, which is why it turns up in so many pairs. Counted across the whole directory it reaches 10 of the other 22 tools, and the integration matrix shows that row against every other.

All 10

Every Clay integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 10 of 10
↔

Clay and HubSpot

Two-way sync
BuiltNativeBuilt on the API
WatchNeeds a higher plan

Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up.

  • Moves: Contacts, Companies, Deals, Lists
  • Needs: Clay Growth or above, where CRM integrations start. Nothing extra on HubSpot.
Needs a higher plan · hours Read the guide
↔

Clay and Salesforce

Two-way sync
BuiltNativeBuilt on the API
WatchNeeds a higher plan

The same read, enrich, write loop, against an org with stricter rules.

  • Moves: Contacts, Companies, Deals, Lists
  • Needs: Clay Growth or above, a Salesforce edition with API access, and a full user licence to authenticate
Needs a higher plan · hours Read the guide
←

Clay and Apollo

One way, in
BuiltNative

A native provider column, and the cheapest first step in most waterfalls.

  • Moves: Contacts, Companies
  • Needs: Any Clay plan, plus your own Apollo account. Clay's catalogue marks every Apollo action as needing one.
Metered by usage · minutes Read the guide
→

Clay and LinkedIn

One way, out
BuiltNative
WatchNeeds a higher plan

An enriched audience pushed into Campaign Manager, people or whole accounts.

  • Moves: Contacts, Companies
  • Needs: Clay Growth or above, a LinkedIn Ads account with billing set up, and a role on that ad account above viewer
Needs a higher plan · minutes Read the guide
→

Clay and Smartlead

One way, out
BuiltNativeBuilt on the API

Push, look up, update and remove, on a campaign Clay cannot create.

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, a Smartlead API key, and a campaign that already exists
Metered by usage · minutes Read the guide
↔

Clay and Attio

Two-way sync
BuiltNative
WatchNeeds a higher plan

Write to objects you defined yourself, rather than to contacts and deals.

  • Moves: Contacts, Companies, Custom objects
  • Needs: Clay Growth or above, an Attio workspace, and an Attio workspace admin to authorise the connection
Needs a higher plan · hours Read the guide
↔

Clay and n8n

Two-way sync
BuiltBuilt on the APIZapier, Make or n8n
WatchNo app, you build itNeeds a higher plan

Webhook out of the table, into a workflow that can wait for an async job.

  • Moves: Contacts, Companies
  • Needs: An n8n instance, and Clay Growth or above, because both halves of this pair are Growth features
Needs a higher plan · hours Read the guide
→

Clay and Outreach

One way, out
BuiltNativeBuilt on the API

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

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, an Outreach contract, and twelve read-write scopes you cannot refuse
Metered by usage · minutes Read the guide
→

Clay and lemlist

One way, out
BuiltNativeBuilt on the API

Three actions, an API key, and a campaign that has to exist first.

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, a lemlist API key, and a campaign that already exists
Metered by usage · minutes Read the guide
Buyer's guide

How to pick, and what to check first

4 things that decide whether a Clay integration will work for you, in the order they usually bite.

01

Import a filtered slice, never the portal

Contacts missing a title, companies with no employee count, deals in an open stage. Pulling everything spends actions on rows that needed nothing and makes the write step far more dangerous than it has to be.

02

Read-only until the columns are right

Lookup actions change nothing. Create and Update are immediately live to every user in the CRM. Run the table read-only, check the raw responses, write to ten rows, open them in the CRM, and only then schedule it.

03

Order the waterfall cheapest first

Because actions bill on the attempt, putting an expensive specialist ahead of a cheap broad provider inverts the economics of the whole table without changing anything anyone would notice in the interface.

04

Decide whether Clay stays in the path

Once the logic settles and an engineer owns it, a direct API call is cheaper with fewer moving parts. Paying two meters for a pipeline nobody has touched in six months is the failure mode worth checking for quarterly.

Written up

The Clay integrations with a full guide

Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.

Other tools

Integrations for the rest of the stack

Connecting Clay is half the job

An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.

Free trial, no card required, and 500 credits to start.

FAQ

Clay integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Is Clay an integration or a tool?

Both, and treating it as an integration is more useful here. Its job in a stack is to sit between a CRM and a set of data sources, which is what a connector does. The difference is that the logic in the middle is editable by a non-engineer, and that is the whole reason to pay for it.

How do I connect a provider Clay does not list natively?

An HTTP API column. Point it at the endpoint, set the auth header, map the response into columns. Reverse Contact is the worked example in this directory and takes about ten minutes.

Why is my Clay bill higher than my match rate suggests?

Because actions are consumed by the attempt rather than the result. If half your rows resolve, your real cost per filled field is twice the action rate. That is not a hidden charge, it is what routing across many providers costs, and it is the argument for putting a cheap high-coverage source first.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 10 integrations 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-09-18
Sources
6 vendor documents
Paid placement
None

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