Brevo Automations
How to Remove a Contact From a Brevo List When a WooCommerce Order Is Refunded
Some lists are only for paying customers — onboarding, product tips, a members-only newsletter. When an order is refunded, the person should come off them. Zapify does this with the An order changes status trigger set to Refunded and the Add or remove a contact from a list action. Brevo is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: An order changes status (
WC_ORDER_STATUS_CHANGED, WooCommerce) - Action: Add or remove a contact from a list (
BREVO_LIST_MEMBERSHIP, Brevo)
When an order changes to Refunded, Zapify removes the customer from the Brevo list you choose. They stay in Brevo as a contact; only the list membership changes.
Before you start
- WooCommerce installed and active.
- A Brevo account (formerly Sendinblue).
- A Brevo API key — a v3 key from SMTP & API → API keys in your Brevo account, not an SMTP key. Brevo's own page for it is here.
- The Brevo list customers were added to, and the contact must already exist in Brevo.
PRO feature
Brevo is a Zapify PRO integration and needs a Connection under Settings → Connections. The WooCommerce trigger used here is free.
How to build the automation
Step 1: Connect Brevo
- Go to Settings → Connections and click Add New.

- Choose Brevo, paste in your API key, and name the connection something like Marketing Brevo.

- Click Test. Zapify asks Brevo whose account the key belongs to and answers with something like Connected to Brevo as Your Company (you@example.com), which catches a key pasted from the wrong account.
- Save.
See Connections for how this screen works generally.
Step 2: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Remove refunded customers from the customers list.

Step 3: Add the "An order changes status" trigger
- Click Add Trigger.

- Choose WooCommerce as the app.

- Select An order changes status.

- Set New status to Refunded. Leave Previous status as Any unless the transition matters.
Step 4: Add the "Add or remove a contact from a list" action
- Click Add Action.

- Choose Brevo as the app.

- Select Add or remove a contact from a list.

Step 5: Configure the action
| Field | Required | What it does |
|---|---|---|
| Connection | Yes | The Brevo connection from Step 1. |
| Add or remove | Yes | Choose Remove. |
| Email address | Yes | Insert the Billing email token. |
| List | Yes | The list to take them off. |
Step 6: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.

Step 7: Test it
Refund a test order for a customer who is on the list. Check the list in Brevo, or Zapify → Logs, which shows … was removed from list ….
Tokens you can use
| Token | What it holds |
|---|---|
| Billing email | The customer's email address. |
| Order number / Order total / Previous status / New status | Details of the order and the change. |
Conclusion
With the An order changes status trigger and the Add or remove a contact from a list action, a refund tidies your Brevo lists without anybody doing it by hand. To keep your CRM in step another way, see removing a Groundhogg tag when an order is refunded.
FAQs
Is this free in Zapify?
The WooCommerce trigger is free. The Brevo action needs an active Zapify PRO licence and a Connection.
Does this delete the contact?
No. It only removes them from the list. To delete a contact entirely, use Delete a contact.
What if they are not on the list?
Brevo reports the change as not made for a contact that is not there, and the log tells you to check that the contact exists.
Does a partial refund count?
This trigger reacts to the order's status. A partial refund usually leaves the order as it was, so it will not fire. Check how your store records refunds.
Why is my new list, attribute or template not in the dropdown?
Zapify keeps the lists, attributes and templates it reads from Brevo for ten minutes, so the builder does not call Brevo on every dropdown. Wait a few minutes and reopen the field. If the dropdown stays empty, use Test on the connection, because an unreachable Brevo gives an empty list.
Do I need to write any code?
No. The API key is the only thing you copy from outside Zapify.