# Send leads to Attio > A chat lead becomes a record on any object in your Attio workspace. Source: https://welcomeai.dev/docs/attio Category: Destinations Updated: 2026-09-11 --- ## What you need An **access token**: Attio, *Workspace settings*, *Developers*, then *Access tokens*. Two scopes matter: - **Record read-write** -- create the record. - **Object configuration read** -- read the objects and their attributes, so the mapper offers fields that exist rather than a list somebody typed. ## Connect and route 1. In **Destinations**, connect Attio with the token. 2. Pick the **object**. Every object in the workspace is there -- People, Companies, Deals, and any you have built yourself. 3. Create a **route** -- which leads it takes, and which object they become. 4. **Map the attributes**, read from that object. ## A value in Attio is a list Attio does not store a scalar. Every attribute holds a **list of values**, each with a shape of its own, and a bare string where one of those belongs is rejected or silently dropped. So each attribute is written the way Attio reads it: - an **email address** becomes `[{ email_address }]` - a **phone number** becomes `[{ original_phone_number }]` - a **name** is split into its halves: `[{ first_name, last_name, full_name }]` - a **domain** is stripped to its host, so `https://acme.com/pricing` is stored as `acme.com` - a **number**, a **date** and a **checkbox** are converted before they are wrapped Anything that cannot be shaped -- a date that is not a date, a checkbox answered "maybe" -- is left out and named in the dispatch log. **Attributes that point at other records** (a reference to a person, a company, a workspace member) are not offered. They need an Attio record id, and a lead answer is a string. ## What it does not do It creates a record. Attio can *assert* on a matching attribute -- create or update, keyed on an email say -- and that is the obvious next step, but which attribute should be the identity is a decision we would rather ask for than choose for you.