Write to objects you defined yourself, rather than to contacts and deals.
Clay Growth or above, an Attio workspace, and an Attio workspace admin to authorise the connection
Contacts, Companies, Custom objects, two-way sync.
The cleanest CRM pair on the Clay hub, because Attio has no fixed object model to fight: the Object dropdown is populated from your workspace, so a custom object is as reachable as People or Companies. Clay provides two import sources and four write actions, three of which cost a credit and one of which, the lookup, is free and is the one the vendor tells you to run first. The real constraints are not features. They are who is allowed to authorise the connection, a write budget on Attio's side that a single request can spend three times over, and the fact that none of this exists below Clay Growth.
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 |
|---|---|---|
| Attio records | One way, in | Import records pulls from any object, narrowed by a saved View or a JSON filter query, sorted, and capped by a Limit whose maximum is 50,000 records. |
| An Attio list | One way, in | Import records from list is the second source, taking a list rather than an object, with the same filter, sort and 50,000 limit. |
| New records | One way, out | Create record writes into any object and costs 1 credit per run. It does not check for an existing match, which is what makes Upsert the safer default. |
| Updated records | One way, out | Update record needs the Attio Record ID, costs 1 credit, and carries a Multiselect Behavior switch that decides whether multiselect values are appended or overwritten. |
| Matched records | One way, out | Upsert record matches on a unique attribute you choose from the writable unique attributes on that object, then updates or creates. 1 credit, and the action to reach for when you are not certain. |
| A lookup | One way, out | Lookup records is free and returns up to 10 matching records. It is a read performed from Clay, so it counts as a call out even though nothing changes in Attio. |
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.
There is no fixed field map, because there is no fixed object model. Clay populates the Object dropdown and the Object Schema from your connected workspace, so what you can write is whatever your Attio workspace holds on the day you build it. What is fixed is which action takes which identifier, and that is the part worth reading twice.
| In Clay | In Attio | What to know about the match |
|---|---|---|
| Import records | Rows in a Clay table | Takes an Object, an optional View, an optional JSON Filter ignored when a View is set, a Sort and a Limit of up to 50,000. |
| Import records from list | Rows in a Clay table | Takes an Attio list rather than an object, with the same filter, sort and 50,000 limit. |
| Create record | A new record in an Attio object | Object plus Object Schema attributes. 1 credit per run. Performs no match, so it will happily create a second copy. |
| Lookup records | Up to 10 matching records | Free. Takes a Record ID or Object Schema filters, and optional JSON path filters to trim the response. Required before a create if you care about duplicates. |
| Update record | An existing record, by Record ID | 1 credit. Requires the Attio Record ID, so it follows a lookup or an import. Multiselect Behavior appends or overwrites multiselect values. |
| Upsert record | A matched or new record | 1 credit. Matches on a writable unique attribute such as email or domain, then updates or creates. The safe default when you are unsure. |
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: six field mappings 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.
The practical reading of this table is that three of the six entries cost a credit and the useful one does not. A build that runs the free lookup first and writes only on a condition is cheaper and safer than one that writes optimistically, and both vendors document that same shape from their own side.
This is not a grid of Attio editions, because Attio does not gate the integration: the constraint on its side is a rate limit and an admin permission, neither of which you can buy your way past. The question is entirely which Clay plan includes CRM integrations, and the answer is the same one that governs every other CRM pair on this hub. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Clay plan | Import Attio records | Write back to an object | Import beyond 250,000 |
|---|---|---|---|
| Free | Not included | Not included | Not included |
| Launch | Not included | Not included | Not included |
| Growth | Included | Included | Not included |
| Enterprise | Included | Included | Included |
Counted off that grid, of twelve pairings: five give you included, seven give you not included. The first two rows read identically again, which is the same sentence this hub keeps having to write: the entry paid plan buys nothing for a CRM pair, so the only upgrade that changes anything is the one to Growth. The Enterprise column differs on volume alone, which is the right shape for a gate: it is a ceiling you can measure against your own record count rather than a feature you are missing.
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
CRM integrations read not included on Free and not included on Launch in Clay's plan comparison, and included from Growth. Attio counts as a CRM here. Check this first, because both the import sources and the write actions are behind the same gate and there is no half-build to start on a cheaper plan.
Clay: a workbook
In a workbook click Add, search for Attio, and you will be asked to Select Attio account. Adding an account runs an OAuth flow that only an Attio workspace admin can complete. Line this up before you start: it is the step most likely to stall a build for a day.
Clay: Import records
Import records takes an Object, with an optional saved View, an optional JSON Filter, a Sort and a Limit of up to 50,000. A View takes precedence and the Filter is then ignored, so pick one deliberately. If you set neither, every record in the object is returned up to the limit.
Attio: the object's attributes
Upsert record matches on a unique attribute chosen from the writable unique attributes on that object, typically an email address or a domain. This is the single decision that determines whether this integration creates duplicates for the next year, so make it explicitly rather than accepting the first option in the dropdown.
Clay: Lookup records
The vendor's own best-practice note says to run the free Lookup records action first to check for duplicates before creating new records. It returns up to 10 matches. Build the table so the write action only runs when the lookup came back empty.
Clay: run settings
Only run if gates the enrichment on conditions you set, and Auto-update syncs new rows back to Attio as they arrive. Add the condition before the auto-update, or the first unattended run writes every row including the ones the enrichment failed on.
Nothing is installed in Attio, so removing this means deleting the connection in Clay. What does persist is whatever you wrote, which is why the matching attribute and the conditional run are the two steps worth slowing down for.
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-attio/SKILL.md https://www.reversecontact.com/integrations-hub/skills/clay-attio.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 person connecting is not an Attio workspace admin. Clay documents that only workspace admins can authorise this connection.
Have an Attio workspace admin run the Add account step. There is no delegated permission for this in Clay, so it has to be them in the browser rather than a scope you can be granted.
WhyA saved View is selected on the same source. Clay documents that the View takes precedence and the Filter is ignored when both are present.
Remove the View if you want the Filter to apply, or move the logic into the View. Nothing warns you about this, so check it first whenever an import returns the wrong rows.
WhyNeither a View nor a Filter was set. Clay documents that all records are returned when neither is provided.
Set one of them, and set the Limit as well. The Limit maximum is 50,000, which is also the point at which an import becomes a modelling problem rather than a configuration one.
WhyCreate record is being used where Upsert record is wanted. Create performs no match and will write a second copy of a record that already exists.
Switch to Upsert record and choose the matching attribute deliberately, or run the free Lookup records first and make the create conditional on it returning nothing. Neither fixes duplicates already there.
WhyMultiselect Behavior was set to overwrite rather than append, so the incoming values replaced the existing ones.
Set it to append on any attribute where Attio is the system of record for values Clay does not know about. This fails silently, so check one record after changing the setting rather than waiting for somebody to notice.
WhyThe write budget is 25 requests a second, and a request that creates referenced records spends more than one: a person with two new companies attached counts as 3.
Read the Retry-After header rather than retrying immediately, and reduce the fan-out by creating referenced records first so later writes only reference existing ones. Identical references within one request are merged and counted once.
WhyAttio states it may reduce the rate limit during incident response, and may permanently lower it for specific APIs that handle a lot of data.
Treat the ceiling as variable rather than fixed. Anything bulk should back off on a 429 and read the endpoint documentation for a lower published limit, rather than assuming last quarter's throughput.
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 October 2024 to May 2026 were read in full on 28 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.
My company is about to onboard Clay. From what my manager and RevOps guy told me we can mass enrich prospects via Salesforce to reduce needing to click around various tools. [...]
r/sales·October 2024·51 points
The most upvoted description of the job this pair does, and note what it is: not enrichment, but not clicking around various tools. That is the test to hold this integration to. If a rep still has to open Attio and Clay and a third tab, the build has not delivered the thing it was bought for.
teh duplicate thing killed us - we had contacts from 3 different sources (web forms, events, manual adds) all creating separate records. [...] we still had to manually merge a bunch. [...] Nobody talks about how much time this eats up before you can even start selling.
r/CRM·April 2026·4 points
Three sources creating separate records is not something an integration causes or cures, which is exactly why the matching attribute is the decision this page keeps returning to. An upsert keyed on a unique attribute stops new duplicates from this path. It does nothing about the ones the web form made last year.
fancy enrichment tools on top of garbage data is just expensive garbage. [...] the duplicate issue alone kills everything downstream. Clay doesn't know its enriching the same person twice [...] data quality is infrastructure, not admin work.
r/CRM·May 2026·2 points
The sharpest statement of why the free lookup matters. Clay does not know it is enriching the same person twice, because nothing tells it: the lookup is how you tell it, and it costs nothing. This is the practitioner version of the vendor's own best-practice note, arrived at the expensive way.
we use Attio. definitely not as robust as some other CRMs but if that's not what you're looking for, then it'll do the job. i feel like the learning curve is also less steep than other platforms
r/gtmengineering·February 2026·3 points
Corroborates the premise of this pair from the user's side. Teams pick Attio because the object model bends to them, which is the same property that makes the Clay integration reach custom objects the day they are created. The trade is the one the commenter names: less robustness than a heavier CRM.
I'm sat here with HubSpot Pro, aircall and... Nothing else! Suspect that Clay would be overkill for us.
r/sales·October 2024·3 points
Worth keeping on the page, because this integration starts at Growth and the question of whether you need it at all is cheaper to ask now than after the upgrade. If the enrichment is one provider filling one field on a few hundred records a month, this is the wrong tool and a CSV is the right one.
Nobody discusses this pair by name, so the search was the job rather than the pairing: getting enriched records into a CRM and keeping them clean. That turns out to be the right question, because almost every complaint in these threads is about duplicates and data quality rather than about either product. One caution on the cache behind this section: the highest-scoring Attio thread is an AMA by the company's co-founder, so most of its replies are the vendor rather than practitioners, and none of them are quoted here.
Four of these five are about data quality rather than about either vendor, which is the corroboration this section is for: the documented advice from Clay and Attio both points at writing less, and the practitioners arrived at the same place by paying for the alternative first.
Attio is the CRM in this directory with the least opinion about what a record is. Any standard or custom object in the workspace appears in Clay's Object dropdown, populated from the connected account rather than from a list Clay maintains, so a bespoke object is reachable on the day you create it. That is the hook for this pair and it is genuinely unusual: most CRM integrations in this directory can write to contacts and companies and then stop.
The advice the two vendors give is the same advice, arrived at from different directions, and it is worth following rather than discovering. Clay's best-practice note and Attio's rate limiting guide both point at writing less:
All three reduce the number of write requests, which is the budget that is genuinely scarce here at 25 a second. The credit saving is a pleasant side effect rather than the point.
The failure this pair is most often blamed for is duplicates, and the blame is usually misplaced. Practitioners describe contacts arriving from web forms, events and manual adds, all creating separate records, and enrichment tools then paying to enrich the same person several times. Nothing in Clay or Attio causes that, and nothing in either will fix it: an upsert keyed on a unique attribute prevents new duplicates and does nothing about the ones already there. Decide which attribute is the key before the first write, because every row after that inherits the decision.
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, Attio 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.
Yes, and it is native on the Clay side rather than an HTTP build. Clay publishes two Attio sources, Import records and Import records from list, and four actions: Create record, Lookup records, Update record and Upsert record. The Clay Attio integration reaches any standard or custom object in your workspace, because the Object dropdown is populated from your connected account rather than from a fixed list. It sits in Clay's CRM integration band, which starts at Growth.
Growth. Clay's plan comparison marks CRM integrations as not included on Free and not included on Launch, and included on Growth and Enterprise, and Attio is a CRM for this purpose. Growth is listed at $446 a month on an annual commitment and $495 billed monthly. There is no partial version on a cheaper plan: the sources and the write actions are gated together.
Create record, Update record and Upsert record each cost 1 credit per run, and Clay states that in the documentation for each one. Lookup records is free, which is the whole reason the vendor's own best-practice note tells you to run it first: checking for a duplicate costs nothing and creating one costs a credit and then costs you again in cleanup.
Because a saved View is selected on the same source. Clay documents that View takes precedence over the custom Filter query and that the Filter is ignored when both are provided, which is a silent precedence rather than an error. Clear the View if you want the Filter to apply. If neither is set, the source returns all records in the object, up to the limit you set.
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.