Skip to content

Brevo Automations

How to Send a Brevo Welcome Email When a New User Registers

If your welcome email is already designed in Brevo, Zapify can send it for you the moment someone registers, with the free A user registers trigger and the Send a transactional email action. Brevo is a Zapify PRO integration.

What this automation does

The automation is one trigger plus one action:

  • Trigger: A user registers (WP_USER_REGISTERS, WordPress)
  • Action: Send a transactional email (BREVO_SEND_TRANSACTIONAL, Brevo)

Whenever a new account is created, Zapify asks Brevo to send your welcome template to that person, with their name filled in.

Before you start

  • 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.
  • An active transactional template in Brevo, with placeholders such as {{ params.NAME }}. Only active templates are listed.

PRO feature

Brevo is a Zapify PRO integration and needs a Connection under Settings → Connections. The A user registers trigger used here is free.

How to build the automation

Step 1: Connect Brevo

  1. Go to Settings → Connections and click Add New.

Open the Connections tab

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

Add the Brevo connection

  1. 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.
  2. Save.

See Connections for how this screen works generally.

Step 2: Create a new automation

  1. In the WordPress admin, go to Zapify → Automations.
  2. Click Add New to open the builder.
  3. Name it clearly, such as Send my Brevo welcome email.

Create a new automation

Step 3: Add the "A user registers" trigger

  1. Click Add Trigger.

Add a trigger

  1. Choose WordPress as the app.

Select WordPress as the trigger

  1. Select A user registers.

Select A user registers

Step 4: Add the "Send a transactional email" action

  1. Click Add Action.

Add an action

  1. Choose Brevo as the app.

Select Brevo as the action

  1. Select Send a transactional email.

Select Send a transactional email

Step 5: Configure the action

Field Required What it does
Connection Yes The Brevo connection from Step 1.
Template Yes Your welcome template.
Recipient email address Yes Insert the User email token.
Template parameters No For example NAME set to the First name token, which fills {{ params.NAME }} in the template.

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.

  1. Set the trigger and every action to Live.
  2. Click Save.

Set the automation live

Step 7: Test it

Register a test account with an address you control and check that the welcome email arrives. Zapify → Logs shows The email was sent to ….

Tokens you can use

Token What it holds
User email / Username / Display name / First name / Last name The new account.
Registration date When they registered.

The action makes one token available to later actions: Brevo message ID.

Conclusion

With the free A user registers trigger and the Send a transactional email action, a Brevo-designed welcome email goes out on its own. Add the same person to a list with Create or update a contact in the same automation, or send the welcome through WordPress itself instead with a welcome email.

FAQs

Is this free in Zapify?

The trigger is free. The Brevo action needs an active Zapify PRO licence and a Connection.

Can I add the person to a Brevo list and send the email?

Yes. Add a second action, Create or update a contact, to the same automation.

The name is empty in the email.

The user may have no first name saved at registration. Use the Display name token, or fall back to the username.

Why did the send fail?

Open Zapify → Logs. The message starts Brevo answered followed by the HTTP status and Brevo's own explanation, such as an inactive template or an unverified sender.

Do I need to write any code?

No. The API key is the only thing you copy from outside Zapify.

Was this page helpful?