Join forces and merge this into the Brevo module? [#3553922]

Problem/Motivation

Coming here from #3471021: Webform newsletter subscription integration checkbox & handler should we merge this into the Brevo module maybe and join forces together as maintainers?

Think that might make sense, also API-wise?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork brevo_webform_handler-3553922

Show commands

Start within a Git clone of the project using the version control instructions.

Add & fetch this issue fork’s repository

Or, if you do not have SSH keys set up on git.drupalcode.org:

Add & fetch this issue fork’s repository

3553922-join-forces-and changes, plain diff MR !1
Check out this branch for the first time

Check out existing branch, if you already have it locally

About issue forks

Comments

Comment #1

22 October 2025 at 19:34

anybody created an issue. See original summary.

Comment #2

stijnstroobants

Dutch

Leuven

commented 23 October 2025 at 06:52

Sounds logic, as long as we don't need to install unnecessary functionalities to only send contacts to Brevo-lists.
I still didn't check the Brevo-module enough

Comment #3

anybody

German

Porta Westfalica

commented 23 October 2025 at 07:48

@stijnstroobants I'd think of a master "Brevo" module that allows storing the API credentials and provides the basic API methods, maybe not even any end-user-facing functionality. Submodules and contrib should then base on that.

We implemented something similar for the Posthog module, if you'd like to take a look.
Please note that I'm not the Brevo module owner or key-maintainer, just using Brevo and try to help with the module roadmap. Where should we discuss that further?

Another alternative would be to keep this in contrib, but use the Brevo module as base for API credentials. But I think it would also be helpful to have you as experienced Brevo developer!

Comment #4

anybody

German

Porta Westfalica

commented 23 October 2025 at 07:51

PS: Furthermore I think that many "base" functionalities might be similar or even the same, so would make sense to share that also on the UI level, e.g. forms. Shouldn't be much different to handle a block for newsletter subscription or a commerce checkout step with newsletter subscription checkbox for example one level deeper. So with a base module common functionality can be shared across all levels?

Comment #5

kensae commented 9 February 2026 at 08:42

I'm also using the brevo module and the brevo_webform_handler would be a useful addition.
I 've added a conditional check for the Brevo module's services. The handler now dynamically detects if the Brevo services are available; if they are, it utilizes them for processing. Otherwise, the logic seamlessly falls back to the existing implementation to ensure uninterrupted functionality.

I'll create a merge request for review.