Clay and Attio integration: full setup walkthrough for 2026

How the Clay + Attio Integration Works

Clay pushes enriched data to Attio in one direction: Clay is the source, Attio is the destination. The integration matches records by email (People) or domain (Companies), creates new records if no match exists, and updates existing ones if a match is found. You control which fields sync and whether empty Clay cells can overwrite populated Attio attributes.

Under the hood, Clay uses Attio's REST API to upsert records. Every time a Clay table row runs through the Attio action, it fires a PATCH or POST to Attio's /v2/objects/people or /v2/objects/companies endpoint. The sync isn't continuous. It's trigger-based: it runs when you explicitly push a row, run a batch, or configure a Clay workflow to auto-push new rows as they enrich.

Attio won't pull updates back to Clay. If a sales rep updates a company's employee count in Attio directly, that change doesn't flow back to your Clay table. The integration is a write pipe, not a sync loop. Teams that need bidirectional sync have to build that separately with Zapier or Make, and it's rarely worth the complexity for most outbound workflows.

How to Set Up the Clay + Attio Integration

Setup takes about 20 minutes if you have your Clay table ready and Attio admin access. The bottleneck isn't authentication. It's deciding which Attio attributes you want to populate and confirming they exist before you try to map to them. Creating attributes mid-setup breaks the flow and forces you to restart the field mapping from scratch.

1. Open your Clay table. Navigate to the table containing the records you want to push to Attio. Build and enrich the table first if you're starting fresh. Pushing incomplete data creates more cleanup work later.
2. Add an Attio action column. Click the + column button, search for Attio, and add the action. Clay offers Create/Update Person and Create/Update Company. Pick based on your target object type.
3. Connect your Attio workspace. Click Connect Account and complete the OAuth flow. You need Attio admin or workspace member access with API permissions. Clay stores the token at the workspace level, so this is a one-time step per team.
4. Set the match field. For People, use email. For Companies, use domain. This is the field Attio uses to decide whether to create a new record or update an existing one. Getting this wrong is the most common cause of duplicates.
5. Map your Clay columns to Attio attributes. Use the field mapper to connect each Clay column to an Attio attribute. Custom attributes must exist in Attio before they appear in the mapper. Create them in Attio's workspace settings first.
6. Choose overwrite behavior. Clay lets you decide whether empty values in Clay can overwrite populated values in Attio. Set this to only update when Clay has a value. It prevents empty cells from wiping out data your team added manually in Attio.
7. Test with a single row. Right-click one row and run the Attio action manually. Check the Attio record to confirm the data pushed correctly and the match logic worked as expected.
8. Enable for the full table or set up auto-push. Once the test passes, batch-run all rows or configure a Clay workflow trigger to auto-push new rows as they finish enriching.

Field Mapping Reference for People Objects

Attio uses a schema-first model: every attribute must exist in Attio before you can write to it from Clay. Default attributes cover the basics. Everything custom needs to be created in Attio's workspace settings before you start mapping. Here's what maps cleanly out of the box for a People object, with the edge cases that trip most teams.

The Company Record Reference field causes the most problems. Clay tries to match company records by name, but name-matching is fuzzy and inconsistent across your data. Push the domain instead and let Attio's domain-matching handle it. Domain matching is exact and reliable. String matching on company names rarely is.

Common Errors and How to Fix Them

Three errors break most Clay-to-Attio setups: a 422 validation error on required attributes, duplicate records from a wrong match-field configuration, and OAuth token expiry that cuts the connection silently without showing any error on the row. Each has a direct fix that takes less than five minutes.

422 Validation Error. This fires when a required Attio attribute is missing or formatted incorrectly. The most common culprits are phone numbers without country codes and location fields sent as plain text instead of structured location data. Check the Attio attribute type in workspace settings and adjust your Clay column formula to match the expected format.

Duplicate Records. Duplicates happen when the match field is wrong or blank. If you're pushing People records and the email column is empty for some rows, Attio can't find a match and creates a new record instead. Add a Clay filter before the Attio action column to only push rows where the email field is populated.

OAuth Token Expiry. Clay's Attio connection token expires after roughly 90 days of inactivity. When it does, the Attio column starts failing silently. No error on the row, no alert, just no data reaching Attio. Fix: go to Clay's integrations settings, disconnect the Attio account, and reconnect. It's a known Attio OAuth behavior, not a Clay bug.

List Assignment Failing. If you're trying to push records directly into an Attio List, the list ID must be a static value in Clay, not a formula output. Dynamic list IDs fail at the API level. Hardcode the list ID or use a separate Attio workflow to assign records to lists after they're created as objects.

Who Gets the Most Value From This Integration

This integration is most useful for outbound-led teams who build targeted account lists in Clay, enrich them with waterfall data sources, then push qualified records to Attio to manage the pipeline. If your workflow ends in Clay, you don't need this. If Attio is where your reps work their deals, it's essential for keeping the CRM current without manual data entry.

Three teams see the clearest return. Account-based outbound teams building 50 to 500 account lists per month in Clay who want enriched records in Attio without manual CSV imports. Revenue ops teams who need a reliable, auditable path from enrichment to CRM record creation. And early-stage founders running outbound themselves who want every prospect that clears a quality threshold in Clay to land automatically in Attio.

Attio is the right CRM for this stack. Clay's enrichment depth combined with Attio's flexible workspace model is the strongest pairing available for outbound-heavy B2B teams right now. Teams running HubSpot or Salesforce should use Clay's native actions for those tools instead. The Attio integration is built for the modern GTM stack, not legacy CRM setups.

Plan Requirements and What It Costs

Clay's Attio integration is available on the Explorer plan at $149/month and above. The free Starter plan doesn't support workflow actions, including Attio push. Attio requires the Plus plan at $34 per user per month (billed annually) or above for API write access. On Attio's free tier, the API is read-only and Clay can't create or update records.

For a two-person team: $149/month for Clay Explorer plus $68/month for two Attio Plus seats comes to $217/month. A junior RevOps hire handling the same enrichment and CRM hygiene manually runs $3,000 to $5,000 a month. The integration pays for itself in the first week. You're not buying software. You're buying back hours your team currently burns on data entry.

Frequently Asked Questions

Does the Clay and Attio integration sync in both directions?

No. Clay pushes to Attio, not the other way around. Changes made in Attio don't flow back to Clay. The integration is a one-way write pipe. For bidirectional sync, you'd need a separate Zapier or Make workflow pulling Attio updates back into Clay.

Which Attio plan do you need for the Clay integration?

You need Attio Plus ($34/user/month, billed annually) or higher. Attio's free plan only supports read-only API access, so Clay can't write records to it. Clay itself requires the Explorer plan ($149/month) or above for workflow actions.

What's the best match field when pushing records from Clay to Attio?

Email for People objects, domain for Company objects. Name-based matching creates duplicates because Attio uses exact string matching. Email and domain matching are far more reliable. Filter out rows with empty match fields before running the Attio action to prevent phantom record creation.

Can you push records from Clay directly into an Attio List?

Yes, but the list ID must be hardcoded in Clay. Dynamic list IDs generated by formulas don't work with the Attio API. Create the record first via the Clay-Attio action, then use a separate Attio automation or webhook to move the record into the right List based on its attributes.