Brevo
Keep existing Brevo contacts updated from Attio, add People to lists, and bring message activity back to CRM records.
Installation and setup
Install the app through its setup page in Neon Deer. The app is available now through those installation links while Attio marketplace approval is pending.
You need an Attio workspace, a Brevo account, access to the app in Neon Deer, and an organization admin to complete setup. Features also depend on your organization's plan and the access your Brevo key permits.
- Open Brevo in Neon Deer and follow its setup page.
- Connect Workspace access for the Attio workspace you want to use.
- Follow the connection link into the Brevo app in Attio, complete the app connection, and return to Neon Deer.
- Add your Brevo API key in the app's settings. Use a standard API key for the Brevo account whose contacts and activity you want to connect.
- Check the account and permissions under Manage API key, then configure contact mappings and enable the sync options you need.
Brevo explains how to create and manage API keys. Only its account owner or a user with API-key permissions can create a key. Copy it when it is created; Brevo does not let you reveal it again. Keep it out of screenshots and support messages.
The access check verifies what the key can read. It does not prove that every write permission is available; writes and webhook changes are checked when used. If the app is not available in your organization, contact us.
Plans
Free includes Attio-to-Brevo contact updates, contact creation, list additions, and template-email sending in Attio, plus email-send events in Attio Activities. Paid and the trial add contact changes from Brevo to Attio, additional message activity, and importing earlier events. For example, delivery and engagement events, SMS, and WhatsApp activity require Paid or the trial.
Your Brevo account and key must also permit the requested operation. Compare platform plans.
Match existing contacts
Contact synchronization does not create People in Attio. A separate email-activity setting can add missing People when an admin enables it, or an admin can add an eligible Person from a waiting Activity. Brevo-to-Attio contact updates only change mapped values on existing, matched People. Contact updates and message activity have separate settings.
Automatic sync updates existing Brevo contacts. It does not create missing contacts or People in Attio. To create a Brevo contact from an Attio Person, use the Create contact record action or Create or update Brevo contact workflow step, as described below.
The Person's first email address is used for the initial Brevo contact match. Contact matching is shown as read-only in Configuration. Other addresses and subscription restrictions can affect later actions, so review a Person's contact identity if the match is held or no longer correct.
When a Person's profile email changes, automatic actions wait for an admin to review it under Contacts to review. Choose Keep profile contact to retain the current Brevo link, or choose the correct contact. The app does not silently relink the Person or treat an email change as permission to resubscribe them.
Map contact attributes
Open Configuration to choose the Attio attributes and Brevo contact attributes that belong together. Mappings are split into Brevo to Attio and Attio to Brevo tables. Choose a value in the table for the direction you need. Mapping the same Attio attribute in both tables shows Syncs both ways. Contact matching is shown separately: Brevo contacts are matched on the Person's first email address.
For example, use Attio to maintain the selected company or customer-segment attributes on a contact that already exists in Brevo. Enable the opposite direction only for attributes you want Brevo to update in Attio.
Use All, Mapped, or Not mapped and search to find an attribute. In Attio to Brevo, a Person's Name offers Full name, First name, and Last name. Map a part to a Brevo text attribute. First and last name can also be read from Brevo's own FIRSTNAME and LASTNAME attributes into the Person's name. Full-name mappings and names from related records remain outbound-only. Names on related records are not offered. System-managed or unsupported attributes show why they cannot be mapped. Review the mapping before turning on automatic contact updates; a mapping decides which values can be written.
You can map a Brevo attribute to one part of an Attio location: a street line, city, region, postal code, country, latitude, or longitude. Map each part separately. For example, share a customer's city and country for regional segmentation without copying their full address.
When Brevo updates an Attio location, unmapped parts stay as they are. Country names are translated to the matching country in the other system. An unknown or ambiguous country is skipped and identified in Activity. Brevo's detected location attributes can be read into Attio, but cannot be written back to Brevo. Incoming mapping still requires the plan feature for Brevo-to-Attio updates.
Status attributes can be mapped by their title, like a single-choice Select. Review Activity if a status title does not match. If creating a new Attio status needs additional access, reconnect Workspace access before retrying the update.
Choose who can act from Attio
An organization admin opens Settings → Who can do this from Attio. Set Create contacts, Add to lists, and Send emails from templates separately to Off, Attio admins, Specific people, or Everyone in Attio. Creating a missing contact while adding to a list needs both actions to be allowed.
The Attio workflows section has a separate switch for each action. Workflows run without an acting person, so restricting record and bulk actions does not turn off the workflow step. New defaults preserve access: everyone can use the record and bulk actions, and workflow switches are on until an admin changes them. Install the latest Brevo app so actions identify the person using them.
API keys and AI connections keep their own permissions; these Attio settings do not grant or remove API/MCP access. Refused actions appear as skipped in Activity with the reason.
Update Brevo contacts from Attio
In Settings → Attio to Brevo, turn on Keep contacts up to date to update existing Brevo contacts when relevant mapped attributes or filter values change in Attio.
Use Contact filters to include the People you want to send and exclude those you do not. These filters apply to automatic updates and updates started by hand. If a Person stops matching, updates stop; that does not remove their contact from Brevo. Filters now offer more exclusions, such as is not one of or does not contain, where the attribute supports them. Negated comparisons leave out empty values, including blank text and empty lists. Use is empty when those values should match.
For a one-time update, find Update all existing Brevo contacts now in Settings → Attio to Brevo and choose Update contacts. It applies the current mappings and the same filters as automatic updates to existing Brevo contacts that match People in Attio. Review the run's updated, skipped, and unconfirmed results afterward. Neither this update nor Keep contacts up to date creates new contacts.
If Merges and deletions from Attio asks you to reconnect the workspace, complete that step before relying on automatic updates and list actions. It gives the app the current Attio access it needs.
For mapped outbound updates, choose whether existing Brevo values can be replaced, blanks should leave an existing value alone, or only empty attributes should be filled. Check that policy before running a one-time update.
An eligible contact update can be undone from Activity. Review the changed attributes and choose which to restore, or undo a completed update of all contacts. Values edited in Brevo afterward are left alone. Earlier updates without backups cannot be undone, and availability is shown on each update. Undo restores Brevo values; it does not change Attio, so a later Attio edit can send those newer values again. Brevo automations may run when values are restored.
Create a Brevo contact from Attio
In the latest Brevo app for Attio, use Create contact from a Person record or a bulk selection. The action creates a contact when no Brevo contact uses that Person's email, or updates the existing contact otherwise. It writes only the mapped attributes.
This action does not change list membership, subscription choices, or blocklists. Contacts with a subscription restriction, an identity hold, or an unverified match cannot bypass that check. Review the action's results before retrying. Automatic sync still updates existing contacts. Workflows can create contacts using the step below. The public API and MCP can also create a missing contact as part of a list addition when requested. They do not offer a standalone contact-create or direct contact-value write operation.
Create or update contacts in a workflow
In Attio's workflow editor, add Create or update Brevo contact and pass the Person the workflow is handling. The step creates a contact when Brevo does not have one, or updates the existing contact. A retry of the same workflow run returns the contact already created rather than creating another.
Use a separate list step when you want to add an existing contact to a Brevo list. A list addition can create a missing contact only when that option is enabled. Review the step outputs to see whether the contact was created or updated and which email or list was used.
The current app no longer includes Add person to Brevo automation list. Review any workflow using that older step and configure the current Brevo list step; do not assume an existing workflow was changed automatically.
Read contact changes back from Brevo
Where your plan includes it, turn on Contact sync under Brevo to Attio and choose when to check for changes. The first check runs after you enable it.
The app updates verified, linked People from the Brevo contacts that have changed. An Attio value edited since the previous check is kept rather than overwritten by that incoming update. Missing or deleted Attio People are not created automatically.
Changes are checked periodically. Do not treat this direction as an immediate, continuous copy of every Brevo edit.
Add People to Brevo lists
Use the available Brevo list action from an Attio Person or a bulk selection, or add the Brevo list step to an Attio workflow. Choose the list and review the result. The current app does not ask for a consent checkbox when adding contacts. This does not clear a subscription restriction.
By default, the action adds contacts that already exist in Brevo. Enable the option to create missing contacts when you want it to create a contact with your saved mappings and add it to the list. This stays off unless you select it. Unsubscribed or blocked addresses are skipped, and the app does not resubscribe them. Adding someone to a list does not grant consent or clear a restriction.
Review the results before retrying unconfirmed items. A skipped contact may need an identity, subscription, or connection issue resolved first.
Send a Brevo template email
In the latest Brevo app for Attio, select People from a record action, a bulk selection, or a workflow step, then choose an active transactional template from your Brevo account with a configured sender. The email goes to each Person's profile address. They do not need an existing Brevo contact, and sending does not create one.
Unsubscribed or blocked profile addresses are skipped without trying another address. An identity that needs review or unavailable unsubscribe checks can also prevent sending. A recently sent matching email is not sent again.
Review each result in Activity. If Brevo did not confirm a send, it is shown as not confirmed and is not resent automatically. Check Brevo before trying another send. A confirmed send does not prove inbox delivery or that someone read the message.
These emails use Brevo templates. For internal alerts to Attio workspace members, use Email Notifications.
Show message activity in Attio
Under Attio Activities, choose the message events you want to copy and enable Sync message activity. Email events are matched by email; SMS and WhatsApp events are matched by phone number. Available channels and engagement events depend on your plan and Brevo access.
Email activity can match any current email address on a Person, not just the first one, as long as it identifies one Person. This is separate from the initial contact match described above. If no Person matches, the event cannot appear in Attio. You can review it in Brevo → Activity in Neon Deer while it waits for a matching Person.
Adding a Person later does not guarantee that earlier events will attach. The app also checks who the address belonged to when the event occurred; a current email match alone is not enough.
Use Sync all to import earlier events for a selected date range, then review its result. An event must be available from Brevo and have a matching record before it can appear in Attio.
Email Activities can show the subject, sender and reply-to, recipient, template or campaign, and who sent it. Enable Include subjects and content when you want the email subject and text copied into Attio; attachments are not copied. The Activity appears with its subject and details first, and its email content is added shortly afterward as Brevo provides it. Content that Brevo no longer keeps is omitted rather than holding back the Activity.
Activity reports describe the events Brevo reported. An open or click event does not prove that a person read or acted on a message. Create and maintain your email templates in Brevo. Send a selected transactional template through the Attio action, workflow step, or API and MCP.
Add missing People from email activity
In the message settings, an admin can choose Opens an email or Clicks a link in an email to add a Person when no Person in Attio has that email address. This is off until enabled. The event must also be selected for activity sync and available on your plan. Workspace access must allow Person creation; the settings explain what needs attention if it does not.
The new Person receives the address and the first and last name Brevo has. Waiting activity for that address is then attached to the record. An eligible waiting email row also offers Add to Attio, even when automatic creation is off. Review the address before confirming.
Addresses that a Person currently has or previously held are not used to create another Person. Neither are addresses currently unsubscribed or blocked in Brevo. Imported earlier events never create People automatically. If Attio does not confirm creation, check the row's result and the offered next action before trying again.
Choose the right contact
Open Contacts to review from its tab or the Overview notice when a Person's contact link needs a decision. It lists one row per Person, their addresses, the Attio record link, and why review is needed.
An admin can open the chooser to compare the contacts' current details from Brevo: name, lists, created and changed dates, subscription restrictions, and recent campaign activity. Choose the contact the Person's updates should use. If details cannot be loaded, the page says so; contact selection is still available. Review the addresses and restrictions before choosing.
Review activity and unsubscribes
Open Activity to see which contact or list was involved, which mapped attributes changed, who started the action, and whether it came from Attio, automatic sync, a workflow, an API key, or an assistant. Earlier entries may not have all of these details.
Use Contacts for individual activity and Runs for an update of all contacts, a bulk contact update from Attio, or an undo. Open a run to review changed attributes and contacts, including values before and after. Admins can undo a whole eligible run or selected attributes. Values changed later in Brevo, and restricted or held contacts, are left alone. Undo does not change Attio; its values can be sent again on a later update.
An update of all contacts shows progress while running. If a mapping or filter stops it, the run names the setting to fix and links to it. If the settings were merely edited while it ran, start the update again. Contacts it did not reach are skipped. Search and filter activity, and use the page footer to jump to another page or change Rows per page. The page address preserves that choice, and large totals can be approximate.
The Unsubscribes tab lists Brevo’s current restrictions: unsubscribes, spam complaints, hard bounces, and blocks. When Brevo reports that an address is subscribed again or a block is lifted, that address’s restriction is released in Neon Deer too. Historical events remain in Activity but do not keep the address restricted on their own. Search for an email address, filter by reason, and follow the linked Attio Person where available. This is a review screen; it does not send messages or clear subscription restrictions.
Each Activity row shows the email address that event or update concerned, when known, and links to its Brevo contact when available. Older rows may have no address; that does not mean the event concerned another address on the Person. Unsubscribes distinguishes All marketing email from All email, which also blocks transactional messages. Manage restrictions in Brevo.
Use unsubscribe data in Attio and workflows
People in Attio can show Brevo’s own email restriction status. No restriction recorded replaces Subscribed, and Status not confirmed means Brevo’s status could not be read. Update any Attio workflow or filter that checks the old Subscribed label. With Brevo and Workflow automations available, use the Brevo unsubscribes lookup table to check an address in an Attio workflow, for example before a notification or handoff step. The table contains Brevo’s restrictions only. It keeps its ID when renamed, so existing workflow lookups remain connected. The name stays as you chose it if you renamed the table.
A restriction belongs to an email address, not the whole Person. Match the address the action will use; do not assume one restricted address means all of a Person's addresses are restricted. A missing row is not evidence that someone consented to receive email. Brevo send actions still enforce their own subscription checks.
You can add your own fields to the table and edit those values. Its rows and supplied fields are maintained automatically; you cannot add or delete those rows or archive the table. Read the lookup-table guide for workflow use.
API and MCP
The Brevo API guide covers contact mappings, sync settings, activity, unsubscribes, list additions, and template email sends. It requires Paid or an active trial and separate alpha access to the Brevo API family. MCP is generally available, but still checks that family's access and the connection's permissions.
API and MCP actions can send a selected transactional template and add People to lists, optionally creating missing contacts. MCP asks the connected person to accept those actions. retry_brevo_activities retries eligible message Activities and unsynced contact updates; its result separates the two counts. See retry behavior and results. The API can update existing contacts through sync and optionally create missing contacts as part of a list addition. There is no standalone Brevo contact-create or direct contact-value write operation. To add a missing Attio Person from eligible email activity, use create_brevo_activity_person with request_key and brevo:execute. MCP asks for confirmation. See Person creation settings for its safeguards and the API reference for the request and result.
In Activity, Not synced identifies contact updates or list additions that failed or were not completed. An admin can retry a Person's latest failed plain update to an existing Brevo contact. Choose Retry all to retry eligible unsynced contact updates matching the current Activity filters. Updates already waiting for a retry are left alone. If more remain, run it again. Each retry uses the current mappings, unsubscribe checks, and contact-identity checks. A row shows whether a later attempt synced, was skipped, is still running, or did not sync; a later skipped attempt does not hide an earlier unresolved update. This does not retry contact-creating actions, list additions, or email sends. Not confirmed is reserved for a template email whose send Brevo did not confirm; it is not resent automatically. Activity rows show the Attio Person and address when available. Person in Attio means the linked record has no available name; an unmatched event is identified separately, and a dash means the event named no Person. The attention indicator highlights message events that have not reached Attio; check Activity for contact-update failures.
Troubleshooting
A result says the Person was not found. A send or list addition for a Person that no longer exists in Attio is skipped. Review the current selection before retrying. Failed contact updates now give a reason explaining whether the run did not finish or the incoming update did not reach Attio.
A contact was not updated. Confirm it already exists in Brevo, check its profile match and mapped attributes, and review the include and exclude filters. Check whether its identity is held for review.
A list addition was skipped. Check for an unsubscribe, blocked address, identity warning, or a missing contact when contact creation was not enabled. Do not try to bypass a subscription restriction by repeating the action.
Access checks fail. Confirm the account, key permissions, and any key-expiry or IP restrictions configured in Brevo. A read check cannot identify every missing write permission. Use Brevo's key guide when replacing the key.
Activities are missing. Check that both Attio connections work, that the relevant event is selected, that activity sync is enabled, and that your plan includes it. Review whether the email address or phone number matches a record.
The initial unsubscribe check is running. Settings shows progress while restrictions are read. Sending can remain unavailable until monitoring is current. Let the check finish rather than attempting to bypass it.
Another app owns the Activity type. Message settings explains the problem and holds messaging. Retry or save the settings after resolving access; the app will not take over another app's Activity type.
A connection needs attention. Follow the reconnect prompt in Neon Deer. If Attio is still removing the previous connection, try again shortly rather than creating repeated connections. Refresh your AI client's tool list after reconnecting.
You cannot change settings. Ask an organization admin to check app access, connections, and the organization's plan.
An Activity was not saved in Attio. Neon Deer checks Attio and retries an unconfirmed Activity under the same write key to avoid a second copy. If the Activity still cannot be confirmed, its result explains the failure and offers a retry. An outgoing template email whose send is unconfirmed is different: check Brevo before sending it again. Contact updates that cannot be verified end without blocking later updates to that address.