Make it possible to subscribe to the pro newsletter

[manon-corneille]

Story: #
Today, When a user creates an account on the Pro platform and ticks “Subscribe to the newsletter”, we do keep the info, but it's not used.
As we are now publishing a newsletter every couple of months from SendinBlue, it would be good to allow users to subscribe to it.

Part of

• 🏭 Producers platform (Tracker issue) #5521

[stephanegigandet]

We use Brevo (which used to go by the name Sendinblue) to manage newsletters.

Here is the documentation for the Brevo API: https://developers.brevo.com/reference/createcontact

[teolemon]

Could this help ?
https://metacpan.org/pod/WebService::SendInBlue

[Ban3]

Could this help ? https://metacpan.org/pod/WebService::SendInBlue

It's for an old version (v2) of the API. Current is v3.

API v2 Deprecation Notice

On June 25th 2020 Sendinblue's API v2 started its official deprecation process. The sunset of the platform will be carried out through the current year and will be completely removed by *December 2022

It doesn't seem to have any functions for contact/campaign management anyway.

[stephanegigandet]

Steps:

• create a free plan on Brevo, and create an API key
• create a contact list on Brevo, and get the list id
• create a Brevo.pm module, with a function add_contact_to_list($list_id, $email, $username, $cc, $lc..)
• create a brevo.t unit test, to verify it works, and to verify, we also need a function to get the list of contacts, or get one contact info
• then use add_contact_to_list() in user.pl or Users.pm when a user creates an account

[stephanegigandet]

Put the Brevo API + the Brevo list id in Config2.pm (not in GitHub) and Config.pm

Something we'll need to figure out is how to have a unit test that can run without a Brevo API key, one way is to mock the API responses (this has been done in other tests)

[github-actions]

This issue has been open 90 days with no activity. Can you give it a little love by linking it to a parent issue, adding relevant labels and projets, creating a mockup if applicable, adding code pointers from https://github.com/openfoodfacts/openfoodfacts-server/blob/main/.github/labeler.yml, giving it a priority, editing the original issue to have a more comprehensive description… Thank you very much for your contribution to 🍊 Open Food Facts

[manon-corneille]

I close this issue as the discussion moved to : #8856