Attio (Edge)

Configure Attio as a Source in your Pipeline

Perform the following steps to configure your Attio Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Attio.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify a Source Name, a unique name for your Source, not exceeding 255 characters. For example, Attio Source.

6. In the Connect to Attio section, click Authorize With Attio.

   

7. Log in to your Attio account, if you are not already logged in.

8. On the Allow Hevo Data to access your workspace page, review the permissions that Hevo requests, and then click Allow. Hevo only reads data from your workspace. After you allow access, Hevo displays the name of your Attio workspace as Account Added.

   

9. Click Test & Continue to test the connection to your Attio Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To ingest a child object, you must also select its parent object. For example, to ingest the Record object, you must also select the Object object. The Data Model lists the child objects of each parent object.

In the first run of the Pipeline, Hevo ingests all the data available for the selected objects in your Attio workspace. In each subsequent run, as per the sync frequency, Hevo ingests all the records of the selected objects again, because the Attio API does not provide a reliable way to read only the changed records. As a result, the time a run takes and the number of API requests grow with the size of your workspace. Hevo ingests the child objects of a parent object along with it.

Hevo reads the records and attributes of each object in your workspace, including custom objects, and the entries and attributes of each list. The value of each attribute of a record or a list entry, including custom attributes, is loaded as a separate row in the Record Value or Entries Value object.

Attio limits the number of read requests to 100 per second. Read Rate limiting. If Attio returns a rate limit error, Hevo waits and retries the request. If the rate limit persists, Hevo skips the object in that run, without loading any of its data, and ingests it in full in the next run. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---