Connect Attio | Docs | Fivo University

Attio is a flexible CRM where deals and companies carry the notes your team writes. Connecting it gives the Brain those records next to your calls and email, linked to the right account.

What it adds to your Brain

Fivo reads your Attio deals and the notes written on them and on companies:

Each deal record: its name, the workspace member who owns it and the values that describe it, together with the company it points at.
Notes on deals and on companies, with the member who wrote them and when.

Each deal becomes a thread, and notes are placed on the deal or company they belong to. Example question: "What did we note on the Helio deal after the demo, and who owns it?"

The deals object is standard in Attio but is not enabled in every workspace. If your workspace does not use it, there are no deals for Fivo to read.

Before you start

You need to be a member of the Attio workspace, with access to the deals and notes you want Fivo to read. Installing an app may require a workspace admin.
When you approve Fivo, Attio asks for permission to read your object configuration, record permissions, lists and list configuration, notes and workspace members, to read and create tasks, and to read and create webhooks. Task creation is used only when you share a meeting report or action items to Attio as tasks. The webhook permission is what lets Attio tell Fivo when a record or note changes.

Step by step

Open Integrations in the app and choose Attio.
Click Connect. Attio opens its authorization page.
Sign in to Attio, pick the workspace and approve the permissions.
Fivo confirms the connection, records your workspace on its own and registers a webhook. There is nothing else to pick: the whole workspace is the source.

What happens next

Fivo reads your deals and then your notes, and the Attio source in the AI Brain view moves from queued to reading to done.

After the first read, new and edited deals and notes arrive live: Attio tells Fivo which record or note changed, and Fivo reads it back. The regular sync pass re-reads the workspace to catch anything the webhook missed.

Who can see what: with organization scope, Attio material is readable by the people who are members of the workspace, matched by email to members of your organization. Attio's per-record permissions are not evaluated, so a workspace that relies on them is answered more openly than Attio itself would. See Permissions: what your Brain can see.

Disconnect

Open Integrations, select Attio and click Disconnect. Fivo removes the webhook it registered in Attio, stops reading and deletes the stored credentials. What the Brain already learned stays in the graph; connecting the same workspace again resumes reading. To take Attio material out of the graph, use Remove from graph on the Attio source in the AI Brain view.

Troubleshooting

"Reconnect to read". The connection was revoked in Attio, or it was made before reading was added. Click Reconnect and approve again.
Nothing appears yet. Check the source in the AI Brain view. If it says "There's nothing to read in this account", your workspace may not have the deals object enabled or has no notes on deals or companies.
An edit is not visible. Edits reach Fivo through the webhook. If the webhook could not be registered, they appear on the next full pass; reconnecting registers it again.
The source takes long to finish. Each pass re-reads the whole workspace because Attio cannot filter by modification date. This is expected on large workspaces.

integration
crm