Attio

This page describes how to use Census with Attio.

Getting Started

Navigate to the Destinations page in Census and click New Destination.
Select Attio from the menu.
Open the Attio app in another browser tab. Navigate to Workspace Settings
1. Select Developers from the left hand menu and click the Create a new integration button.
2. Once the integration is created, a new access token will be available within your new integration. Copy this value.
3. Ensure your access token has Read/Write access for Record as well as Read access for Object Configuration and Read access for User Management under the Scopes section.
Return to Census and paste the access token under API Token.

Supported Objects and Behaviors

Object Name

Supported?

Sync Keys

Behaviors

Company

✅

Any unique attribute

Update or Create

People

✅

Any unique attribute

Update or Create

Custom Objects

✅

Any unique attribute

Update or Create

Attio supports Don't Sync Nulls. Syncs created prior to August 20, 2024 will need to be updated to sync nulls.

Record References

Fields of type Record Reference are taken in as an array of objects. Below is an example of the expected format:

[
    {
        "target_object": "companies",
        "target_record_id": "<company uuid>"
    },
                    {
        "target_object": "people",
        "target_record_id": "<person uuid>"
    }
],

Attio Name Attribute

Attio supports two syntaxes for writing name values: string and object (recommended). Census supports both via Liquid templating:

String
- The format must match last name, first name.
- Liquid example:
```
"name": "{{ record ['last_name'] }}, {{ record['first_name'] }}"
```

Object

There are three properties that all must be set: first name, last name, and full name
Liquid example:

{
    "first_name": "{{ record['first_name'] }}",
    "last_name": "{{ record ['last_name'] }}",
    "full_name": "{{ record['first_name'] }} {{ record['last_name'] }}"
}

Census will recognize an object is being sent by the opening { in the second example.

Need help connecting to Attio?

PreviousAttentive NextAutopilot Journeys

Last updated 2 months ago

Getting Started

Navigate to the Destinations page in Census and click New Destination.

Select Attio from the menu.

Open the Attio app in another browser tab. Navigate to Workspace Settings

Select Developers from the left hand menu and click the Create a new integration button.
Once the integration is created, a new access token will be available within your new integration. Copy this value.
Ensure your access token has Read/Write access for Record as well as Read access for Object Configuration and Read access for User Management under the Scopes section.

Return to Census and paste the access token under API Token.

Supported Objects and Behaviors

Object Name

Supported?

Sync Keys

Behaviors

Company

✅

Any unique attribute

Update or Create

People

✅

Any unique attribute

Update or Create

Custom Objects

✅

Any unique attribute

Update or Create

Attio supports Don't Sync Nulls. Syncs created prior to August 20, 2024 will need to be updated to sync nulls.

Record References

Fields of type Record Reference are taken in as an array of objects. Below is an example of the expected format:

[
    {
        "target_object": "companies",
        "target_record_id": "<company uuid>"
    },
                    {
        "target_object": "people",
        "target_record_id": "<person uuid>"
    }
],

Attio Name Attribute

Attio supports two syntaxes for writing name values: string and object (recommended). Census supports both via Liquid templating:

String

The format must match last name, first name.
Liquid example:

"name": "{{ record ['last_name'] }}, {{ record['first_name'] }}"

Object

There are three properties that all must be set: first name, last name, and full name
Liquid example:

{
    "first_name": "{{ record['first_name'] }}",
    "last_name": "{{ record ['last_name'] }}",
    "full_name": "{{ record['first_name'] }} {{ record['last_name'] }}"
}

Census will recognize an object is being sent by the opening { in the second example.