Connect Attio
- Go to Integrations in the Clustr dashboard and select Attio.
- Click Connect Attio. You’ll be redirected to Attio to authorize access.
- Once authorized, you’ll be returned to Clustr with your workspace connected.
Only one CRM can be active at a time. If HubSpot or Salesforce is already connected, disconnect it before connecting Attio.
Enable the Widget
After connecting, you need to add the Clustr widget to your Attio record layouts. This is a one-time setup per record type; repeat for people, companies, and deals.1
Open the page configurator
Open any people (or company, or deal) record in Attio. Click the ⋯ menu in the top-right corner, then select Configure page.
2
Add the Clustr widget
Click + Add widget. A widget picker opens. Under Apps, select Clustr Network Insights.
3
Save
Close the configurator. The Clustr widget now appears on all records of that type.
How It Works
People and companies in Attio are automatically matched to your Clustr network via domain and LinkedIn URL. Each widget shows who in your network can make an introduction, ranked by confidence.
- A confidence score for the referral path
- The connector who can make the introduction and how they’re connected
- Shared work history and recent engagement signals
- A View All in Clustr link to explore the full list
Settings
Once connected, you can configure write permissions and field mappings from the Attio integration settings page.Write to Attio
Field Mappings
Clustr maps its internal data model to your Attio attribute slugs. The defaults match Attio’s standard schema. Change them only if your workspace uses custom attributes. People
Companies
Deals
The Email field is fixed to
email_addresses and cannot be remapped. Attio requires this attribute for contact deduplication.Owner sync
Clustr’s Owner column can stay in step with an Attio attribute, per record type. Attio has no owner attribute on companies or people — only deals carry a standardowner — so there is nothing to sync until you pick one. Open
Integrations ▸ Attio ▸ Field mappings and set the Owner row on the
Companies and People tabs. The picker lists actor-reference attributes, the
ones that hold a workspace member; “Show all fields” escapes that filter. Only
admins can save a mapping. The Owner column’s gear on each table opens the same
row and shows everyone else a read-only line.
Each record type gets its own direction:
“Also update in Attio” starts unticked, every time. Leave it unticked and
the new owner is saved in Clustr only; the cell then says it differs from Attio,
and a later sync does not overwrite it. Over the API the same choice is
push_to_crm on Set Account State,
Bulk Set Account State and
Set Connector Owner, and the response’s
crmPush says what happened.
Things worth knowing:
- A record that is not in Attio has nothing to write to. The push is refused
with
record_not_matched, and the owner is still saved in Clustr. - Clearing an owner is never pushed.
- An actor that is not a person counts as empty. An
api-tokenorsystemactor on the attribute reads as no owner. - A push overwrites the attribute rather than appending to it, so a multi-select actor reference ends up holding the one owner Clustr wrote. A multi-value attribute read back takes its first value.
- Someone who owns records in Attio but has no Clustr login still appears in
your owner directory. List Owners reports a
crmSeatper owner, so you can tell in advance whether a push can name them. - Warm intros are never synced. No CRM has an object for an intro.
- Turning a mapping on offers a one-time reconciliation: take Attio’s owners, push Clustr’s, or leave the two different.
Tier sync
An account’s tier can be mapped to one Attio company attribute. Attio has no standard field for it, so teams add a single-select attribute. Set it up in Settings ▸ Tiers, under the tier list, or from the Tier column’s gear on Accounts. Match each tier to one option, leaving “Not in your CRM” on any tier that should stay out, then choose the direction: Clustr sets the value, Your CRM sets the value, or Paused. Two tiers cannot share one option.- Clustr sets the value: the tier is written on each sync, not on every edit. An account with no tier, and a tier with no option, are skipped rather than cleared. An attribute that has become read-only, multi-select or deleted is refused at sync time.
- Your CRM sets the value: the attribute is read off every matched company, and Attio’s record webhook also brings a change in between syncs. An unchanged value does nothing, so a tier edited in Clustr survives; a changed one sets the Clustr tier when it maps to a tier you have. Empty and unmapped values leave the Clustr tier alone.
Attio reports its select options per attribute, so the editor reads them
live when you pick the field, and shows up to 25 of them.
Sync
Click Sync Now to trigger a manual sync between Attio and Clustr. The integration also syncs automatically in the background.Mark clients from Attio
Tell Clustr which Attio companies are your clients, and it fills your client companies list from them. In the app, open Targeting > Clients and set either or both of:- a company attribute and the values that mean “client”
- Has a won deal: a deal in one of the deal stages you tick as won. Attio has no won flag of its own, so you pick at least one stage, for example Won. A stage you leave unticked never makes a company a client.