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.
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.
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.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for freeFour native actions on Clay credits, and no Reverse Contact account needed to start.
Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up.
The same read, enrich, write loop, against an org with stricter rules.
A native provider column, and the cheapest first step in most waterfalls.
An enriched audience pushed into Campaign Manager, people or whole accounts.
Push, look up, update and remove, on a campaign Clay cannot create.
Write to objects you defined yourself, rather than to contacts and deals.
Webhook out of the table, into a workflow that can wait for an async job.
Four actions, and the one that matters adds an enriched row to a sequence.
Three actions, an API key, and a campaign that has to exist first.
4 things that decide whether a Clay integration will work for you, in the order they usually bite.
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.
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.
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.
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.
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.
Four native actions on Clay credits, and no Reverse Contact account needed to start.
One way, in → 02Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up.
Two-way sync → 03The same read, enrich, write loop, against an org with stricter rules.
Two-way sync → 04A native provider column, and the cheapest first step in most waterfalls.
One way, in → 05An enriched audience pushed into Campaign Manager, people or whole accounts.
One way, out → 06Push, look up, update and remove, on a campaign Clay cannot create.
One way, out → 07Write to objects you defined yourself, rather than to contacts and deals.
Two-way sync → 08Webhook out of the table, into a workflow that can wait for an async job.
Two-way sync → 09Four actions, and the one that matters adds an enriched row to a sequence.
One way, out → 10Three actions, an API key, and a campaign that has to exist first.
One way, out →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →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.
The questions that come up before anyone opens a setup guide.
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.
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.
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.
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.