Skip to content
Attio

Connector · CRM and email lists

Attio, in every client’s workflows.

Add or update a person, update a person, with the client’s own Attio account.

Triggers
0start a workflow
Actions
2steps in a workflow

Do it in Attio

A step with its own fields: values from the run go in by name, and what Attio answers is there for the next step.

  • Add or update a personCreates the person, or updates the one with this email.
  • Update a personSet a person’s job title, description or other single-value attributes, found by record id. Attributes not named keep their value.

Connect the client’s Attio

On the client’s page in Thrum: Add credential, type Attio access token.

In the client’s Attio: Workspace settings → Developers → New integration → scopes record_permission read-write and object_configuration read → copy the access token.

The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.

Attio’s API documentation

Watched like everything else

When Attio stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request
Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause
Given it, up to an hour
Requests at once, per account
2, per worker; the rest wait their turn
Timeout
15 seconds, unless the step sets its own
Private and internal addresses
Refused, on every redirect too
The client’s key
Encrypted, bound to the client, and kept out of every run record
A step that keeps failing
Marks the workflow Degraded and alerts you, not the client

Attio and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.