Connect Attio

≈ 2 min Extension Bearer Token

Before you start

• An Attio workspace where you are an admin.
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Attio

Set it up

1. Create the token. In Attio, open Workspace settings › Developers, create an integration and copy its access token. Give it read and write access to records and notes.

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Attio in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Attio Under Integration App / Service, pick Attio. There is no Auth Type menu: Attio uses a Bearer Token.
   2. 2 Step 2:Name it For example Attio – CRM. A Description is optional.
   3. 3 Step 3:Paste the token Paste the token into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Attio; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Person › Search with an email you know: the record comes back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to api.attio.com. AWFlow’s servers never relay the call.

Privacy & your data →

Common issues

• “401 Unauthorized — the API key is missing or invalid”. The token is wrong or was revoked. Create a new one and update the credential.
• “403 Forbidden”. The token lacks read or write access to records or notes. Change its scopes in Attio.
• The run is blocked in the web app. Attio runs through the browser extension. Install the extension and allow Attio for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Attio node

All connections

Create and manage credentials

Privacy & your data