> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/attio.md). # Attio Use Attio workflow steps to match, create and update people, companies and deals. ## Connect An admin opens **Settings → Integrations → Attio** and enters the **Workspace access token**. The token needs record and object configuration permissions for the intended Attio workspace. Saving introspects the token to confirm that it is active and identify the workspace. It does not read or change your business records. ## Configure a step Select Attio Match, Create or Update and choose the supported object. Map the identifier or record ID and the fields you need from workflow inputs or earlier steps. Use Match before Create when you want to retain an existing record. Branch explicitly on No match. For Update, use an Attio record ID returned by the lookup; an email address is not an interchangeable record ID. Review the destination's attribute types and required values. A person attribute and a company attribute with similar labels can still have different IDs or accepted values. ## Verify Simulate representative matched and unmatched cases. Then make a controlled live run and inspect the Attio record and field values. A connection failure can mean an inactive token, wrong workspace or missing scopes. A step failure after a successful connection can mean invalid attributes, missing permissions for that operation or a provider validation error. Attio workflow actions are distinct from the HubSpot/Salesforce CRM mirror. Connecting Attio does not automatically import every Attio record into Distro Records. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/attio.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.