- Issue created by @Anybody
- πΊπΈUnited States Chris Matthews
Hi Julian, great questions ...
Currently, the nonprofit I work for is attempting to raise funds to have this module developed so no work has been done just yet.
The main difference between this module and SendinBlue β is that this module won't depend on the Library API β and Entity API β as it will do one thing ==> send transactional email via Brevo's HTTP API only (no SMTP). I'm trying to keep the module super lean and simple so that it's easily maintainable by our nonprofit.
I have not asked Brevo for sponsoring, but I'll do some research to see if that might be a possibility.
- Status changed to Fixed
about 1 year ago 5:55am 19 September 2023 - π©πͺGermany Anybody Porta Westfalica
Thanks @Chris Matthews for the detailed reply! :)
it will do one thing ==> send transactional email via Brevo's HTTP API only (no SMTP)
Thanks, that's important to know and I saw you added that to the module page.
I thought it would for example provide Brevo Subscription forms and e.g. allow syncing users subscriptions by eMail address.
Thanks for the update!
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
3 months ago 2:21pm 28 August 2024 - π«π·France Renrhaf π Strasbourg π¦π¦
Hi there, Brevo has agreed for small sponsoring of the module to provide as a starting point the transactional email API feature.
So we can consider this module as the "official" Brevo one, since they might want to keep it up to date as well and provide some more sponsoring for additional features. We, at SaaS Production, will also sponsor some time of development for this module to implement some missing features for some of our clients.On the roadmap of future features, we can already foresee the two following things :
- Newsletter subscription forms
- Drupal commerce integration (pushing events to Brevo when users are adding products to cart, ordering, etc.)
Don't hesitate to share feedback and missing features that you would need.
Thanks!