# Create Attio people from qualified leads URL: https://useembers.com/help/integrations/attio/ Category: Integrations Plan: Solo and above Updated: 2026-10-28 Last verified: 2026-10-28 > Connect one Attio workspace with the Embers app or an API key and get a person, an optional list entry, and a note when a lead qualifies. Embers can keep Attio in step with your LinkedIn pipeline. When a lead qualifies, Embers creates a person in Attio, can add them to a list you pick, and attaches one note on why the lead matters. A person you already have is updated instead, without touching what your team wrote. > **Warning: Solo and above, administrators only** > > Integrations require Solo or above, and only an Embers workspace admin can connect Attio or change what it receives. Connecting with the Embers app also needs an **Attio** workspace admin. One Attio workspace per Embers workspace. ## Connect Attio ### Open the Attio page Open **Integrations** in the sidebar (`/integrations`) and choose **Attio**. ### Connect with the app or an API key **Attio app** Choose **Connect Attio**. Attio's consent screen opens. Only an Attio workspace admin can approve it, because the connection belongs to the whole workspace, not to one person. If you cancel there, nothing is connected. When you approve, you return to Embers. The app button appears only when Embers has it configured. An API key always works. **API key** An Attio workspace admin creates a key in Attio under **Workspace settings**, then **Developers**. Give it these scopes: - `record_permission:read-write` and `object_configuration:read`: required. Without them Embers cannot add people and refuses the key. - `note:read-write`: for the note. Without it, the note is skipped. - `list_entry:read-write` and `list_configuration:read`: for the list. Without them, leave the list unset: Embers cannot add anyone to it, and delivery pauses until you pick none. Paste the key into Embers. Embers checks it with Attio before storing it, so a key Attio refuses, or one that was revoked, fails here and nothing is saved. It is stored encrypted and never shown again. Either way, Embers reads your workspace's name, which person attributes it may write, and your lists of people. Attio tokens and keys do not expire, so there is nothing to renew. ### Pick a list and what to send Set the options in [What Embers writes](#what-embers-writes), then choose which events to send. New leads are sent by default; a known lead engaging again, changing status, or having a [company change](/help/leads/company-changes/) can update the same person too. ### Send a test A test checks that Attio still accepts the connection, re-reads your lists, and checks the list you picked still exists. It writes nothing to Attio. If the connection was revoked or the list was deleted, the test fails and the install pauses. Reconnecting the same Attio workspace keeps your settings. Connecting a different workspace clears the list you picked. ## What Embers writes **A new person** gets Attio's own attributes: | Attio attribute | Where it comes from | | --- | --- | | Name | The lead's first, last, and full name. A lead with no name fails on its own. | | Email addresses | The stored email, when Embers already has one | | Phone numbers | The stored phone, when Embers already has one | | Job title | The lead's title | | LinkedIn | The lead's LinkedIn profile URL | | Primary location | The lead's location, which Attio reads as text | | Description | The lead's LinkedIn headline | | Company | See **Link the company** below | Empty values are never sent. Attio fills some attributes itself and does not let anyone else write them; Embers reads which on connect and leaves those alone. If Attio refuses one value, such as a location it cannot read, Embers sends the person without that attribute, so the person still lands. **A person you already have** gets only what is safe to change: a new job title, the LinkedIn URL when they have none, and an email or phone Embers has that they do not, added beside theirs. Their name, location, description, and company are never touched, and nothing is sent when nothing changed. Email and phone are sent only on a paid plan, and never looked up for Attio: [contact details](/help/outreach/lead-enrichment-and-contact-info/) are not part of the [free trial](/help/account-and-billing/free-trial/). Three settings control the rest: - **Add people to a list** (none): one of your Attio lists of people. Each person Embers sends is added to it once. Pick another list later and people sent from then on are added to the new one. Lists of companies are not offered. - **Link the company** (on): when a new person has no work email, Embers links the Attio company named exactly as their company, and creates it when there is none. With a work email, Attio links the company from the email's domain on its own, so Embers leaves it to Attio. When two Attio companies share that name, the person is created without a company. - **Add a note** (on): the first time Embers sends a person, it adds one note titled "Qualified by Embers" with the score, the ICP verdict, the top signals, the reason for the match, the LinkedIn profile, the headline, the company's size and industry, and a link to the lead in Embers. A note Attio refuses does not stop the delivery. Embers does not create deals, write your custom attributes, set an owner, or read anything back from Attio. ## How an existing person is found In this order, the first match wins: 1. **The person Embers linked before** in this workspace. If it was deleted, Embers drops the link and keeps looking. 2. **A person with the lead's email**, when Embers has one. 3. **A person with the lead's LinkedIn URL**, written with or without `https://`, `www.`, or a trailing slash. When several people have it, the oldest wins. 4. **Nobody**: Embers creates the person and remembers it, so every later send and retry updates that same record. Attio treats an email as unique, so if another tool created the same person a moment earlier, Embers matches that record rather than making a second. If you end up with two records, merge them in Attio. ## Who gets delivered Attio has its own [delivery rules](/help/integrations/delivery-rules/): a minimum lead score, ICP matches only, the sources that count, and titles and industries to exclude. A lead the rules hold back writes nothing to Attio and is listed in the delivery log as held back, where you can send it anyway. To send leads now rather than wait for the next qualifying event, push them with [Send to](/help/leads/send-to-destination/). ## Send the leads you already have Attio gets a lead when it first qualifies, so leads Embers found before you connected never reach it on their own. **Send existing leads** sends every qualified lead that is not linked to a person in this workspace yet, best score first. Your rules apply, anyone already sent is skipped, so running it again only sends what is missing, and each lead is written exactly like a new one. It cannot start while delivery is off or paused, or while a run is going. ## Delivery log, retries, and pauses The delivery log keeps 30 days of deliveries, each linking to the person in Attio. Failed, blocked, and held-back rows can be retried. Embers keeps to 10 requests a second per connection, well under Attio's own limits. Rate limits, Attio outages, network errors, and a record another request was changing at the same moment are retried: the first attempt plus seven retries, from 30 seconds out to about 6.3 days. When Attio says how long to wait, Embers waits at least that long. A lead Attio refuses for its own values, such as two people already holding its LinkedIn URL, or a lead with no name, fails on its own, and Embers keeps sending the others. These pause the install. Attio pauses send no email, so check the page: - **Reconnect Attio**: Attio no longer accepts the connection. The app was uninstalled or the key was revoked. - **A missing permission**: the connection lacks a scope Embers needs. - **The workspace's plan**: Attio refused for billing reasons, or the workspace reached its plan's record limit. - **Pick another Attio list**: the list Embers adds people to was deleted or is out of reach. Picking another list, or none, clears the pause. - **"Attio paused after 5 leads in a row were rejected"**: five leads failed with none delivered in between, counted from the last resume. The message names the last reason. Fix the cause, then resume. [Attio delivery is paused](/help/troubleshooting/attio-delivery-paused/) walks through each one. **Disconnecting from Embers** stops all writes and forgets the token. An app connection is also revoked in Attio; an API key stays in Attio until an admin deletes it there. Everything already in Attio stays. ## Troubleshooting **The API key is refused.** It was copied incompletely, revoked, or lacks `record_permission:read-write` or `object_configuration:read`. Create a key with those scopes. **No list is offered.** The workspace has no list of people, or the connection lacks `list_configuration:read`. Create the list in Attio, check the scopes, then reopen the list picker. **A job title or location did not arrive.** Attio fills that attribute itself and does not let Embers write it, or Attio could not read the value. The rest of the person still arrives. **The same person appears twice.** The lead had no email, and the existing record held a different LinkedIn URL. Merge them in Attio. ## Related - [Fix Attio delivery when it is paused](/help/troubleshooting/attio-delivery-paused/): What each pause means and how to resume. - [Control which leads reach each destination](/help/integrations/delivery-rules/): Decide which leads are worth an Attio record. - [Send a lead to a destination](/help/leads/send-to-destination/): Push the leads you pick, now. - [Reveal a lead's email and phone](/help/outreach/lead-enrichment-and-contact-info/): Where email and phone come from. ## Frequently asked questions **Do I need to map fields for Attio?** No. Attio people already have a LinkedIn attribute, a job title, and the rest of what Embers sends, so Embers writes to Attio's own attributes and there is nothing to map. **Does Embers create deals in Attio?** No. Embers creates or updates a person, can add them to one list you pick, and adds one note. Create the deal in Attio when you are ready. **Will a test create anything in Attio?** No. A test checks that the connection is still active, re-reads your lists, and checks the list you picked is still there. It writes nothing. **Does Embers rename a person I already have?** No. A person you already have keeps their name, location, description, and company. Embers updates their job title, adds a LinkedIn URL when they have none, and adds an email or phone they do not have yet. **Can I connect two Attio workspaces?** No. One Attio workspace per Embers workspace. An agency connects each client workspace to that client's Attio separately.