> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/attio.md).

# Attio

Generate an Attio access token and connect the Appmixer Attio connector.

The Appmixer Attio connector uses **API key** authentication. You do not need to register an OAuth app. Each user creates an access token (Attio also calls it an API key) in their Attio workspace and enters it when they connect Attio in Appmixer.

***

## 1. Generate an access token

Only **workspace admins** can create access tokens. If you are not an admin, ask one to do these steps for you.

1. Log in to [Attio](https://app.attio.com).
2. Open the dropdown next to your workspace name and click **Workspace settings**.
3. Open the **Developers** tab.
4. Click **+ New access token** and give the token a name (for example `Appmixer`).
5. Set the token's **Scopes**. A new token has no scopes, so grant the ones listed below.
6. Copy the token. You can copy it again later from the **Developers** page by clicking the token.

Attio access tokens do not expire. A token belongs to one workspace and acts as the whole workspace, not as one member. You can edit its scopes or delete it at any time: click the three dots next to the token and choose **Edit** or **Delete**.

### Scopes

Set the scopes in the token dialog as follows, so that every Attio component works. The table follows the order of the dialog in Attio:

| Scope in Attio            | Access     | Used by                                                                                                                                                                                                                                      |
| ------------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| User Management           | Read       | **List Workspace Members**, and the task components (assignees)                                                                                                                                                                              |
| Records                   | Read-write | Create, update, upsert, delete, get and find records (**Create / Update / Create or Update Person**, **Find People**, the same for Companies, and the generic Record components for any object), **Search Records**, and the record triggers |
| Object Configuration      | Read       | **List Objects**, **List Attributes**, and every component that works with records, notes, tasks or files                                                                                                                                    |
| List Entries              | Read-write | **Add Record To List**, **Update List Entry**, **Remove Record From List**, **Find List Entries**, **New List Entry**, **Updated List Entry**                                                                                                |
| List Configuration        | Read       | **List Lists** and all list entry components                                                                                                                                                                                                 |
| Comments                  | Read-write | **Create Comment**, **Delete Comment**                                                                                                                                                                                                       |
| Notes                     | Read-write | **Create Note**, **Delete Note**, **Find Notes**, **New Note**                                                                                                                                                                               |
| Tasks                     | Read-write | **Create Task**, **Update Task**, **Delete Task**, **Get Task**, **Find Tasks**, **New Task**                                                                                                                                                |
| Meetings                  | Disabled   | Not used by the connector                                                                                                                                                                                                                    |
| Call Recordings           | Disabled   | Not used by the connector                                                                                                                                                                                                                    |
| Files                     | Read-write | **Upload File**                                                                                                                                                                                                                              |
| Activity Configuration    | Disabled   | Not used by the connector                                                                                                                                                                                                                    |
| Activity Records          | Disabled   | Not used by the connector                                                                                                                                                                                                                    |
| Sequence unsubscribe list | Disabled   | Not used by the connector                                                                                                                                                                                                                    |
| Webhooks                  | Read-write | All triggers (**New Record**, **Updated Record**, **Deleted Record**, **New List Entry**, **Updated List Entry**, **New Note**, **New Task**)                                                                                                |

**Get Workspace** works with any scopes. You can grant fewer scopes if you only use some of the components. A component whose scope is missing fails with an Attio `403` error that names the missing scope. **Make API Call** needs whatever scopes the endpoint you call requires; each endpoint in the [Attio API reference](https://docs.attio.com/rest-api/overview) lists its "Required scopes".

{% hint style="info" %}
If you add scopes to a token that is already connected in Appmixer and the components still fail with `403`, create a new access token with the scopes above and reconnect the Attio account in Appmixer with the new token.
{% endhint %}

***

## 2. Connect in Appmixer

When you add an Attio component to a flow, Appmixer asks you to connect an account. Paste the token into the **Access Token** field.

Appmixer sends the token as a Bearer token to `https://api.attio.com/v2`. To check the token, it calls `GET /v2/self`. If Attio reports the token as not active (for example, it was deleted), the connection fails. The connection is named after the Attio workspace.

***

## 3. Triggers

You do not need to set up webhooks in Attio yourself. When a flow with an Attio trigger starts, Appmixer uses the token to register a webhook in Attio (`POST /v2/webhooks`) that points at the flow's webhook URL. When the flow stops, Appmixer deletes that webhook.

* Your Appmixer API must be reachable from the public internet so that Attio can deliver webhook calls.
* The token needs the `webhook` scope (read-write), plus the read scope of the data the trigger watches. The trigger loads the full record, entry, note or task through the API with the token after each event.
* **Updated Record** and **Updated List Entry** fire once per changed attribute. If one edit changes several attributes, the trigger fires several times.

***

## Rate limits

Attio allows 100 read requests and 25 write requests per second for each token. The connector queues requests to stay at 20 requests per second per Appmixer user, and Find components return at most 500 items (**Search Records** at most 25).

***

## Backoffice configuration

Configuration ID: `appmixer:attio`. For how to set connector configuration values, see [Connector Configuration](https://docs.appmixer.com/getting-started/services).

You do not need any Backoffice configuration to authenticate, because every user enters their own access token. There are two optional keys:

* `listCacheTTL`: optional. How long, in milliseconds, the lists of objects, attributes, lists and workspace members shown in the inspector dropdowns are cached. The default is `120000` (2 minutes).
* `outputFilePrefix`: optional. A prefix for the names of CSV files created when a Find or List component (**Find Records**, **Find People**, **Find Companies**, **Search Records**, **Find List Entries**, **Find Notes**, **Find Tasks**, **List Objects**, **List Attributes**, **List Lists**, **List Workspace Members**) runs with the **Store to CSV file** output type. Files are named `<prefix>-<component label in the flow>.csv`. The default is `attio-objects-export`.

```bash
appmixer service-config set appmixer:attio -u -d '{
  "listCacheTTL": 120000,
  "outputFilePrefix": "attio-objects-export"
}'
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/attio.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
