# Attio to Brevo Contact Sync

Source: https://neondeerdata.com/docs/integrations/brevo-to-attio-sync/

Push selected Attio People attributes to Brevo contacts. Attribute changes trigger updates, and routing rules assign contacts to Brevo lists.

## Requirements

A Brevo v3 API key, existing destination lists in Brevo, and the Attio People attributes to use for triggers and field mapping.

## Setup

If the integration is not installed in your workspace, [request setup](https://neondeerdata.com/contact-us/?topic=integration-brevo-to-attio-sync).

1. **Choose triggers and destinations** Confirm which People attributes trigger updates, the Brevo destination lists, field map and contact identifier.
2. **Create a Brevo v3 API key** Create the key in Brevo account settings. The app validates access before continuing.
3. **Install the custom Attio app** Add the key in Workspace Settings. Re-provision refreshes the configured fields and routing.
4. **Provision fields and triggers** The app creates the Brevo contact ID field, prepares select options, registers the selected Attio triggers and checks destination lists.
5. **Start sync** Changes to configured attributes push the contact to Brevo. Use Push to Brevo for selected existing People.

For the API key step, see [Brevo's guide to creating API keys](https://help.brevo.com/hc/en-us/articles/209467485-Create-and-manage-your-API-keys).

## Configuration

| Setting            | Configuration                                                                 |
| ------------------ | ----------------------------------------------------------------------------- |
| Trigger attributes | People attributes whose changes push updates to Brevo.                        |
| Destination lists  | Brevo lists to receive contacts.                                              |
| Routing            | Attribute-based rules for one or multiple lists.                              |
| Field map          | Attio values and their Brevo contact attributes, including category options.  |
| Identifier         | Email by default. SMS or an external identifier can be configured separately. |
| Historical import  | Existing People to push, and a separate import for larger data sets.          |
| Inbound events     | Optional opens, clicks, bounces or unsubscribes to write back to Attio.       |

## Sync behavior

### Triggers

Only changes to the configured People attributes trigger a push. For example, a billing-tier change can update Brevo while an unrelated note change does not.

### Contact updates

The default identifier is email. Existing contacts with that email are updated; otherwise a contact is created. The Brevo contact ID is saved on the Attio Person when available.

### Contact ID write-back

The app manages the Brevo ID field. Updating that field does not trigger another push.

### List routing

The default destination is one Brevo list. Conditional routing and multiple lists can be configured. Moving between lists includes removal from the previous list when that rule is configured.

## Limitations

- The default direction is Attio to Brevo. Opens, clicks, bounces and unsubscribes require a separately configured inbound flow.
- Changing a Person's email can create a new Brevo contact. The old contact remains unless cleanup is configured.
- The Attio bulk action supports up to 250 selected records. Larger backfills use a separate import.
- Changed Brevo category options, fields or trigger rules require Re-provision.

## Troubleshooting

### A Brevo select option is missing in Attio

Use Re-provision after changing Brevo category options. It refreshes the select values and checks the field map.

### An attribute change did not sync

Check that the attribute is included in the configured trigger set. Changes outside that set do not push the contact.

## Useful links

- [Brevo](https://www.brevo.com/)
- [Brevo help center](https://help.brevo.com/hc/en-us/)