Connect Drupal Webform. Send every lead to Brevo.

Connect Drupal Webform to Brevo

ClickSyncr sends Drupal Webform submissions to a Brevo list. Connect your account inside the webform, match its fields, and save the handler to prepare new submissions for delivery.

What you need

Use Drupal 10.3 or Drupal 11, Webform 6, and PHP 8.3 or later with OpenSSL. You also need a Brevo account, an API key, and a list to receive subscribers. Keep Webform submission storage enabled and Drupal cron running: the module sends saved delivery requests when cron runs.

Install and open the handler

Install and enable Webform Integration for Brevo from Drupal.org. Open Structure > Webforms, choose your form, and select its Brevo tab. The tab opens the handler configuration. If more than one matching handler exists, choose the handler you want to edit.

Connect your API key

Paste your key into Brevo API key and select Connect. Then choose the Brevo list. The field mapping options load for that destination. To replace a saved key, paste the replacement and connect it before saving the configuration.

Map the fields you collect

Email is required and has its own mapping. The other choices are your Brevo account’s normal contact attributes. Their names come from Brevo, rather than a fixed set of name fields. Supported attribute types include text, number, boolean, date, and multiple-choice values. Map only attributes offered after connecting.

For each destination field, select the matching element from your webform. Start with Email, then review the optional mappings. Check the displayed field types as well as their names so that a date or number is connected to the intended value.

Set consent and subscriber status

Under Consent and delivery, select a Consent checkbox if your form uses one. Once selected, that checkbox must be checked for a submission to be sent to Brevo. Leaving it unselected allows valid submissions through without a checkbox condition. The current handler offers Active as its subscriber status. Confirmation email behavior depends on your Brevo settings; do not treat the consent checkbox as a promise that a confirmation email will be sent.

Test a completed submission

Submit the public form using a test contact you control, with the configured consent checkbox checked. After cron runs, open the saved submission’s Brevo tab and inspect its delivery result. Check the contact in your selected list, including each mapped value. If you configured consent, submit another test with it unchecked and confirm that it is not sent.

Resolve connection and mapping errors

“Could not connect to Brevo.” Check the API key and reconnect; the error message confirms that the saved mapping has not changed. “Could not load this list.” Reconnect and select the destination again. If the account has no lists, create one in Brevo, then reconnect.

If saving asks you to refresh fields and lists, reload them and review the selected sources. A saved submission is not proof of delivery. Read its result before trying again, then correct the reported value or setting. An authorized administrator can use Send again from the submission’s delivery screen.

See the Brevo integration overview for the destination’s ClickSyncr page.

Frequently asked questions

What happens to the saved Brevo API key if Drupal’s hash salt changes?

The module encrypts the saved Brevo credential with a key derived from Drupal’s hash salt. Changing that salt means the old encrypted value cannot be opened with the new key. Reconnect the Brevo API key after the change, then test the handler again. A copied database alone does not recreate the encryption context needed to read the saved credential.

Does Send again use the original Brevo mapping or the current one?

Send again rebuilds the delivery from the submission’s current saved values and the current handler mapping. The consent rule and handler conditions must still pass. It does not replay the original request unchanged. Review the earlier Brevo result before confirming: an unresolved earlier delivery may still complete, and the retry form rejects deliveries already marked accepted or still pending.

How can I tell which mapped fields Brevo accepted or dropped?

Open the saved submission’s Brevo tab and read the Fields column alongside Delivery state and Reason. When the service returns field details, the module shows how many fields were kept and names dropped fields with their reported reasons. An empty Fields cell means no field summary is available; it does not establish that every mapped value was accepted.