Connect Attio to Rig

    Sync companies, people, deals, notes and meetings out of your Attio workspace, along with the full stage history behind every deal. The stage history is the part worth the trouble: it is what turns time in stage from an estimate into something you can measure.

    Requirements
    Attio workspace access that can reach Developers in workspace settings
    Time required
    5 mins

    Create the API key

    1. In Attio, open Workspace settings.
    2. Go to Developers and create a new integration.
    3. Grant it read access to records, notes and lists. For lists, that means both list_configuration:read and list_entry:read, which are separate boxes.
    4. Copy the access token.

    Scopes are set on the integration, not on the key
    If you later find a stream is empty, you do not need to mint a new token. Go back to the integration in Developers, add the scope, and the existing key picks it up. That is the opposite of how most of the tools in this section work, and it saves a round of credential swapping.

    Connect it in Rig

    1. In Rig, open Connections and go to Sources & actions.
    2. Search for Attio and open the card.
    3. Attio API key: paste the token.
    4. Click Test, then Sync.

    What Rig pulls in

    Attio lands in its own attio schema, in eight tables.

    • Companies, People and Deals: the three standard objects, with their attributes flattened into ordinary columns rather than left inside the nested envelope Attio returns them in.
    • Deal stage history: one row per stage a deal has been in, with the interval it was there, so time in stage stays measurable rather than being a snapshot of the stage each deal is in now.
    • Notes and Meetings: the activity attached to those records.
    • Lists and List entries: your lists and what is on them. These two are the only streams that need the list_configuration:read and list_entry:read scopes, and without both they come back empty while everything else still syncs.

    Troubleshooting

    • Lists and list entries are empty, everything else is fine: the two list scopes are missing. Add list_configuration:read and list_entry:read to the integration and the next sync fills them.
    • The key is rejected outright: it was copied partially, or the integration was deleted in Attio. Tokens are shown when created, so mint a new one rather than hunting for the old.
    • Time in stage looks wrong for old deals: query the deal stage history table rather than the stage timestamp on the deal itself. The column on the deal is current-stage-only by design.
    • A column you expected is not there: attributes become columns, so an attribute that is empty across every record has nothing to infer a column from. Fill one record and it appears on the next sync.

    What people use this for

    • Analyse deal velocity across the Attio pipeline
    • Report on your custom fields and lists
    • Surface relationship and engagement signals

    More ideas for using Attio

    Was this guide helpful?