Brevo WordPress Integration: Add a Form Subscriber to a List

A Brevo WordPress integration, for a form, creates or updates a contact and can drop that contact on one list. Core Forms does that with an API key and a list ID. It does not capture SMS consent and it does not map arbitrary Brevo attributes.

I build Core Forms. The fields in this guide are the ones on the Brevo integration page.

What you need

• A Brevo API key from SMTP and API in the Brevo account.
• The list ID if the contact should join a list. Leave it empty and you still create the contact.
• A form with an email field. First and last name are optional and come from the name field you select.

The action upserts by email. A second submission from the same address updates the contact instead of duplicating it.

Add the action

1. In Brevo, create an API key under SMTP and API.
2. On the form, add the Brevo action.
3. Paste the key and, if you want a list, the list ID.
4. Choose the email field and the name field.
5. Save and submit a test from an address you can see in Brevo.

Turn on background processing if you want a failed request retried. The contact is not “in the list” until Brevo accepts it, so the confirmation message should match what your account actually sends. If Brevo double opt-in is on, say so.

What this action does not do

No SMS consent field. No custom attributes. If the list depends on a dozen Brevo properties, this action is the wrong tool. Create the contact here and enrich it in Brevo, or use a workflow that can map those attributes.

It also does not subscribe someone to several lists from one action. One list ID. A second list is a second step you build outside this form, or a second action only if you have deliberately set the form up that way and checked it.

Pick the list that already exists

If the audience is already in Mailchimp or Kit, use that action instead of moving everyone. The Mailchimp guide and the Kit guide cover those. MailerLite is the same shape of action if that is the tool you pay for.

A list that should never leave WordPress does not need Brevo. MailerPress keeps the subscribers on the site.

FAQ

How do I connect Brevo to a WordPress form?

Create a Brevo API key, add the Brevo action on the form, paste the key and an optional list ID, and map the email and name fields. Submit a test and look in Brevo, not only in the WordPress success message.

Can the form set Brevo custom attributes?

Not with this action. Email, name and one list are the fields it sends.

Does the action send the double opt-in email?

Brevo decides that from the list and the account settings. The form does not have a separate double opt-in switch for this action. Write the confirmation to match the rule you turned on in Brevo.