A client collects sign-ups in Brevo, through a form on their site or an imported spreadsheet, and runs the rest of the business from an Airtable base. Sooner or later they ask for every new subscriber to show up in that base too, so the team can follow up, tag them or count them. Thrum has a starter for exactly this, set off by Brevo the moment someone joins a chosen list. Other tools can do it as well, and the first two sections cover what their own pages say.
Zapier
Zapier's Airtable and Brevo page lists templates in both directions. Two of them go from Brevo into Airtable, "Create new Airtable records every time new contacts are added to a specific list in Brevo" and "Add new Brevo contacts to Airtable as records instantly". Its Brevo events include one that fires when a contact is added and one for contacts who unsubscribe from a campaign. Going the other way, templates such as "Add Brevo subscribers for new records in Airtable" push rows into Brevo.
Airtable's "When webhook received" (data from outside)
Airtable can receive data from another service without any middle tool. Its "When webhook received" trigger (the event that starts an automation) gives you a unique address to paste into the other service's webhook settings, and each request that arrives starts the automation, whose later steps can create a record. Airtable's limits for it are 100 KB per request and five requests a second, and every request that starts a run counts toward the automation run limits of the workspace's plan. Airtable also cautions that anyone who has the address can start the automation, so share it carefully.
Whether Brevo can post its list events to an address like that, and in what shape, is a question for Brevo's help centre. Brevo may also have its own way of sending contacts to Airtable, described there.
The Thrum way
The starter is called "Create a record in Airtable when a contact joins a list in Brevo". When you switch it on, Thrum registers itself with the client's Brevo using the client's key, and Brevo then tells it about each join within seconds. Nothing has to be pasted into Brevo by hand.
- Install from the library. Go to Templates → Library, open the starter and install it into the client you are working for. It is switched off on arrival and comes with a checklist.
Connect Brevo. In the client's Brevo, open the account menu, then SMTP & API, then API Keys (Brevo's name for its access keys), and generate a new key. Paste it in as the client's Brevo connection (Thrum stores it encrypted in that client's workspace).
Connect Airtable. Make a token at airtable.com/create/tokens with data.records:read and data.records:write, and give it access to the client's base.
Fill in three fields. "Brevo: List ID" is the number shown beside the list's name under Contacts → Lists. "Airtable: Base ID" comes from the base's address, the part that starts with app. "Airtable: Table" is the name of the table that receives the rows.

- Match the column names. Each join writes one row with three values. "Their email" holds the subscriber's address, "Lists it joined" holds the list's ID, and "When" holds the time Brevo gives for the event. Airtable only accepts names that match the table's columns exactly, so either add columns with those names or rename the three in the step to the client's own, such as Email, List and Joined.

- Switch it on and test. Add yourself to the list through the client's signup form. The row appears in Airtable within seconds.
Things that behave in a particular way
Each join is one row, once. Brevo sends no unique number with these events, so Thrum treats the event type, the email and the time together as the event's identity. If Brevo delivers the same event twice, the second copy starts nothing.
Creating a row is not repeated blindly. When Airtable is busy or has a server error, the step is tried again after 5 seconds and then at doubling waits, up to 3 attempts. If the connection drops after the request reached Airtable, the row may already exist, so Thrum stops and says so, and you retry the run once you have looked.
Turning it off unregisters it. Switching the workflow off, or changing its starting event or the Brevo key, removes the old registration from the client's Brevo, so a paused workflow leaves nothing listening.
Related ways to join the two
Brevo has two more starters that write to Airtable. "A contact's details change" also arrives within seconds, and "A new contact is added" is checked every 15 minutes and records the contact's email, when it was created and whether it is unsubscribed from email. Starting from Airtable instead, new or edited rows can set off a plain-text Brevo email, sent from an address the client has verified with Brevo. The Airtable and Brevo page lists each of them with its starter.
Checked on 14 November 2026.
Sources



