Brevo - Action Update or create company doesn't work anymore

Hi ​@Thierry V. 

You can try this:

1. Open your Zap and locate the Brevo action step that has "Create or Update Company"

2. Delete that entire action step from your Zap

3. Add a new Brevo action and search for "Add or Update Company" - select it

4. Re-map your company data from Chargebee to the fields in this new action (company name, attributes, etc.)

5. Turn your Zap back on and test it with a real Chargebee record

The re-mapping step is important - even though the actions look similar, you'll need to set up the field connections again between your Chargebee trigger and Brevo.

Documentation: How to get started with Brevo (formerly SendinBlue) on Zapier

Hope this helps you get it sorted!

If you're still running into issues after trying these steps, feel free to drop a screenshot of the error and a quick description of what your Zap is doing—happy to take a look and help troubleshoot.
 

This issue usually occurs when an app developer updates their API or deprecates specific endpoints, causing older Zap actions to lose field mapping and fail. To fix this, first try refreshing your connection by going to the "Apps" section in Zapier and reconnecting your Brevo account. If that does not resolve the issue, you will need to replace the broken action. Try deleting the current Brevo step and adding a fresh "Create or Update Company" step to pull in the latest API configuration. Alternatively, if Brevo has rolled out a new version of their Zapier integration, look for a newer version of the Brevo app in your Zap editor and recreate the step there.

Hi!
Thanks for your messages. Here is what I did:
- I reconnected with Brevo
- I created a new step after reconnecting (step 4 in the screenshots)
- I selected a real record
- I verified that the data in the `cf_Nom_Brevo` field matches the company name in Brevo exactly
The mapping still isn't appearing.
I have attached screenshots.
Thanks for your help.

Hi,

I opened a ticket. Zapier confirmed to me that there is a bug and that a fix is ​​in progress.
Thanks everyone for your help.

Hi ​@Thierry V. 👋 Thanks for following up to let us know Support confirmed it's a bug and a fix is in progress!

While that's being fixed, it's worth trying Troy's suggestion to use a Brevo API Request action. Let us know if you get stuck or need any help setting that up.

And if anyone else is running into this, leave a reply here and I'll add you to the list of folks being affected so you get an email notification once it's resolved.