> ## Documentation Index
> Fetch the complete documentation index at: https://docs.1eye.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Attio

> Connect Attio to 1eye, select target lists, map buyer and company fields, then run your destination workflow and verify each delivery in the Console.

Push buyers and companies from your 1eye target lists into Attio. This guide takes you from connecting your workspace to mapping fields, running the workflow, and checking delivery in the Console. Buyers sync to People in Attio.

### Before you begin

* Admin or Marketer access to your 1eye workspace.
* An Attio workspace admin who can authorize the connection.
* At least one [Target List](https://docs.1eye.ai/target-lists/overview.md). To verify a push, use a list with eligible buyers.
* Valid work emails for buyers and company domains for companies. These identify matching records in Attio.

You connect through Attio's sign-in and authorization flow. You do not need to generate an API key or write code. The screenshots use Snowbricks as an example workspace.

### Connect Attio

**Step 1: Create the destination workflow**

1. Open **Destinations** in your 1eye workspace.
2. Select **Add Destination**.
3. Enter a workflow name, such as **Push to Attio**, and select **Attio**.

The workflow follows **Start → Target Lists → Attio → End**.

**Step 2: Open the Attio node**

Select the **Attio** destination node. If it shows **Not Connected**, select **Connect**.

![Attio destination node showing Not Connected and the Connect button](https://mintcdn.com/1eye/q93__e2_3311Ijgq/images/attio-connect.png?fit=max\&auto=format\&n=q93__e2_3311Ijgq\&q=85\&s=6923c55f323343636b74df41caf121e5)

**Step 3: Authorize your Attio workspace**

1. In the 1eye confirmation, select **Yes, continue**.
2. Sign in on Attio's authorization screen.
3. Choose the Attio workspace you want to use, review the requested permissions, and approve access.
4. Return to 1eye. Confirm that the node shows **Connected** and that **Attio account** displays the correct workspace.

### Target Lists node

Select the **Target Lists** node, then:

1. Choose one or more 1eye target lists.
2. Choose **Delivery behavior**:

| Option | What it pushes |
| - | - |
| **Going forward** | New buyers as they are identified. |
| **Push retroactively** | Existing buyers in the selected lists, then new buyers going forward. |

3. Select **Save Target Lists**.

![Target Lists node with a selected list, delivery behavior options, and Save Target Lists](https://mintcdn.com/1eye/q93__e2_3311Ijgq/images/attio-target-lists.png?fit=max\&auto=format\&n=q93__e2_3311Ijgq\&q=85\&s=a6117247e7bebee9f627de5c66579db6)

### Choose an Attio List (optional)

Return to the **Attio** node. Under **Account**, use **Attio List (optional)** to select an existing, compatible Attio List.

* Leave it blank to sync People and Companies without adding list entries.
* Select a People list to add synced people to it, or a Company list to add synced companies.

> [!NOTE]
>
> A **1eye Target List** selects which buyers to push. An **Attio List** organizes records after they reach Attio. 1eye does not create Attio Lists for you.

![Connected Attio account with the optional Attio List selector](https://mintcdn.com/1eye/q93__e2_3311Ijgq/images/attio-select-buyers.png?fit=max\&auto=format\&n=q93__e2_3311Ijgq\&q=85\&s=48016f9a6039e83c089a94613270060b)

### Field mapping

The Attio node has four sections: **Standard Buyer Fields**, **Custom Buyer Fields**, **Standard Company Fields**, and **Custom Company Fields**.

**Standard Buyer Fields**

Review the standard mappings and keep **Push** checked for each field you want to send. Uncheck optional fields you want to exclude.

| 1eye field | Attio field |
| - | - |
| Work Email | Email addresses |
| First Name | Name |
| Last Name | Name |
| Title | Job title |
| Phone | Phone numbers |
| LinkedIn | LinkedIn |
| City, State, Country | Primary location |
| Company Name | Company |

First and last names populate the corresponding parts of Attio's Name field. City, state, and country populate Primary location. The Company field links the person to their matched company.

Keep **Work Email → Email addresses** enabled for buyer matching.

![Standard Buyer Fields with Push checkboxes and the Save Destination button](https://mintcdn.com/1eye/q93__e2_3311Ijgq/images/attio-map-buyer-fields.png?fit=max\&auto=format\&n=q93__e2_3311Ijgq\&q=85\&s=cae9efb3d1e168f619d12a071ebe9577)

**Custom Buyer Fields**

1. Select a **1eye Field**.
2. Select an existing, compatible **Attio Custom Property**.
3. Select **+ Add more** for another mapping.

For example, you could map Persona Name to a text attribute or Target Page Visit Count to a number attribute. Create those attributes in Attio first; 1eye does not create custom attributes automatically.

**Standard Company Fields**

Review the company mappings and their **Push** checkboxes.

| 1eye field | Attio field |
| - | - |
| Company Name | Name |
| Company Website | Domains |
| Company Description | Description |
| Company LinkedIn | LinkedIn |
| City, State, Country | Primary location |

Keep **Company Website → Domains** enabled for company matching.

**Custom Company Fields**

Choose a 1eye company field and an existing, compatible Attio company custom property, just as you did for buyers. For example, map Employee Count to a number attribute you have created in Attio.

![Standard Company Fields and Custom Company Fields in the Attio destination node](https://mintcdn.com/1eye/q93__e2_3311Ijgq/images/attio-map-company-fields.png?fit=max\&auto=format\&n=q93__e2_3311Ijgq\&q=85\&s=6dd28b25a2579123ba4b424ac3840ebf)

Select **Save Destination** when you have finished reviewing the Attio List and all field mappings.

### Run the workflow

1. Open the **Start** node.
2. Choose **Runs continuously**, **Runs until the selected date**, or **Runs once only**.
3. Select **Save Workflow Settings**.
4. Confirm that your target lists and destination settings are saved, then select **Run**.

For an initial test with buyers already in a target list, choose **Push retroactively** in the Target Lists node and **Runs once only** in the Start node.

1eye matches People by email address and Companies by domain, updating matching records instead of creating a new record on each push. Only enabled and mapped fields are sent.

### Monitor pushed records

Select **View console** in the workflow. Filter by **All**, **Pushed**, **Pending**, or **Failed**.

| Status | What it means |
| - | - |
| **Pushed** | All configured operations succeeded, including the Attio List entry if you selected a list. |
| **Pending** | The record is queued, waiting for a retry, or needs a fix to its data or configuration. |
| **Failed** | Delivery could not complete, or retries were exhausted. Open the record for details. |

Select a record to inspect the mapped values sent or attempted, its Attio record IDs, and any response or error. When available, follow the Attio record link to verify the person, company relationship, and mapped fields.

If you selected an Attio List, check that the record also appears in that list. A list-entry error can leave delivery incomplete even when the Person or Company already exists in Attio.

### Disconnect Attio

1. Open the workflow and select the **Attio** node.
2. Open the **⋮** menu next to **Connected**.
3. Select **Disconnect**.

Disconnecting stops workflows that use this connection. People and Companies already pushed remain in Attio. To restore access, reconnect to the intended Attio workspace.

### Best practices

* **Start with one small target list.** Check a few Pushed records in Attio before adding more lists.
* **Review fields before running.** Keep matching fields enabled and map custom fields to compatible attributes.
* **Check Pending records.** Open the details to see whether a record needs data, a mapping change, or reconnection.

### Troubleshooting

| Issue | What to check |
| - | - |
| Connect does not open an authorization window | Allow pop-ups for 1eye, then select Connect again. |
| Connection shows Reconnect Required | Open the Attio node's menu, select Reconnect, and authorize the intended workspace. |
| No buyers appear in the Console | Confirm a target list is selected and contains eligible buyers. Choose Push retroactively to include existing buyers, save, and run the workflow. |
| Buyer or company cannot be matched | Check for a valid work email or company domain and keep its matching field enabled. |
| A field is missing in Attio | Confirm Push is checked, the source value is populated, and you selected Save Destination. |
| Custom mapping cannot be used | Confirm the Attio attribute exists, is writable, and has a compatible type. Create it in Attio first if needed. |
| Selected Attio List is unavailable | Select an accessible, compatible list, or clear the optional selection, then save the destination. |

### FAQ

> [accordion] Does 1eye see my Attio password?
>
> No. You sign in and approve access on Attio's own authorization screen.

> [accordion] Can I change field mappings after the workflow starts?
>
> Yes. Open the Attio node, update the mapping, and select Save Destination. Newly queued pushes use the latest saved mapping.

> [accordion] Does this sync changes from Attio back to 1eye?
>
> No. This destination sends data from 1eye to Attio.

> [accordion] What happens when a buyer leaves a target list?
>
> Records already pushed remain in Attio. Leaving a 1eye target list does not delete the Person or Company, or remove an existing Attio List entry.

### Next step

See [Managing Destinations](https://docs.1eye.ai/destinations/managing-destinations.md) for more workflow guidance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.