---
title: "Clay integrations: read your CRM, call anything, write it back"
description: "Clay integrations for a sales stack. What Clay reads, what it writes, how it connects tools with no marketplace app, and what the action meter really costs."
url: https://www.reversecontact.com/integrations-hub/clay-integrations
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# 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.

- **10** integrations checked

- **9** built natively

- **4** sync both ways

- **5** need a plan upgrade

## 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](https://www.reversecontact.com/integrations-hub/stack/orchestration) and the [data layer](https://www.reversecontact.com/integrations-hub/stack/data) 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](https://www.reversecontact.com/integrations-hub/integration-matrix) shows that row against every other.

## 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.

### [Clay and Reverse Contact](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-reverse-contact-integration)

One way, in

Featured

Built: NativeBuilt on the API

Four native actions on Clay credits, and no Reverse Contact account needed to start.

- **Moves:** Contacts, Companies
- **Needs:** A Clay account. Your own Reverse Contact key is optional and changes which meter you spend.

Metered by usage · minutes [Read the guide](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-reverse-contact-integration)

### [Clay and HubSpot](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clay-integration)

Two-way sync

Built: NativeBuilt on the API

Watch: Needs 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](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clay-integration)

### [Clay and Salesforce](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-clay-integration)

Two-way sync

Built: NativeBuilt on the API

Watch: Needs 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](https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-clay-integration)

### [Clay and Apollo](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-apollo-integration)

One way, in

Built: Native

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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-apollo-integration)

### [Clay and LinkedIn](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration)

One way, out

Built: Native

Watch: Needs 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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration)

### [Clay and Smartlead](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-smartlead-integration)

One way, out

Built: NativeBuilt 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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-smartlead-integration)

### [Clay and Attio](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-attio-integration)

Two-way sync

Built: Native

Watch: Needs 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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-attio-integration)

### [Clay and n8n](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-n8n-integration)

Two-way sync

Built: Built on the APIZapier, Make or n8n

Watch: No 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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-n8n-integration)

### [Clay and Outreach](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-outreach-integration)

One way, out

Built: NativeBuilt 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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-outreach-integration)

### [Clay and lemlist](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-lemlist-integration)

One way, out

Built: NativeBuilt 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](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-lemlist-integration)

## 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.

### 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.

### 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.

### 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.

### 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.

## 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.

01

### Clay and Reverse Contact

Four native actions on Clay credits, and no Reverse Contact account needed to start.

One way, in →

02

### Clay and HubSpot

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

Two-way sync →

03

### Clay and Salesforce

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

Two-way sync →

04

### Clay and Apollo

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

One way, in →

05

### Clay and LinkedIn

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

One way, out →

06

### Clay and Smartlead

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

One way, out →

07

### Clay and Attio

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

Two-way sync →

08

### Clay and n8n

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

Two-way sync →

09

### Clay and Outreach

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

One way, out →

10

### Clay and lemlist

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

One way, out →

## Integrations for the rest of the stack

### HubSpot

17

The hub most sales stacks are actually built around.

See the 17 integrations →

### Salesforce

12

The widest integration surface, gated by edition.

See the 12 integrations →

### Attio

3

A CRM with a data model you write yourself.

See the 3 integrations →

### Reverse Contact

22

People and company data for every tool in this directory.

See the 22 integrations →

### ZoomInfo

3

Deep native CRM integrations, sold by tier.

See the 3 integrations →

## 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.

## [Reverse Contact](https://www.reversecontact.com)

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](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

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

### Read from

- [Reverse Contact API documentation](https://docs.reversecontact.com/getting-started)
- [Reverse Contact: credits](https://docs.reversecontact.com/guides/credits)
- [Reverse Contact: rate limits](https://docs.reversecontact.com/guides/rate-limits)
- [Reverse Contact pricing](https://www.reversecontact.com/pricing)
- [Clay integrations: ReverseContact](https://www.clay.com/integrations/data-provider/reversecontact)
- [Clay docs: Reverse Contact integration](https://university.clay.com/docs/reverse-contact-integration)

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
