Integration of Email Automation with Brevo API

We are eager to start with email automation and integrate our processes with the Brevo API. We maintain a user base where users are created via our website and app. These users can either be free members or become paid members after making a purchase. Below, we describe our requirements and the corresponding user scenarios:

1. Create a new user and add it to a list

Requirement: When a new user registers via the website or app, we want to automatically create this user in our user base and add them to a specific Brevo list (e.g., « Free Members » or « Paid Members »).

User scenario: A user signs up via the app. Their details (such as name, email, and registration date) are sent to the Brevo API, and the user is automatically added to the « Free Members » list. A welcome email is then sent.

2. Update profiles via API

Requirement: User profiles in Brevo should be easily updated via the API, such as when changing their name, email address, or role.

User scenario: A user changes their email address in the app. This update is sent via the API to Brevo, ensuring their profile remains up-to-date and future emails are sent to the correct address.

3. Add purchases (or multiple purchases) - most important part

Requirement: We want to link purchases (and products) to a profile, including the purchase date, expiry date & product name, to send targeted emails (e.g., purchase conformations + renewal reminders).

User scenario: A user purchases an annual subscription. The API adds this purchase to their profile with an expiry date one year later. The user automatically receives an offer to renew one month before the expiry date.

Side note: At Spotted by Locals, a user can purchase multiple products with unique expiration dates (e.g. different city guides with end dates); what would be the best way to solve this?

Thank you in advance!

@qlambert Could you or one of your colleagues, please help and advise?

Hi @jorn , thanks for posting on this community.

If I get it well, you’d like to:

  • add a contact attribute to your contact base, called let’s say « Expiry date »
  • update this attribute with the API: you can do it this way: Update contact attribute
  • and then, launch an automation based on this

For the automation part, you can:

About this:

a user can purchase multiple products with unique expiration dates

For the moment, I don’t think Brevo attributes can’t have multiple values, so you’ll probably prefer to create one contact attribute per product, ex:

  • EXPIRY_DATE_1 for the first product purchased
  • EXPIRY_DATE_2 for the second product purchased
  • EXPIRY_DATE_3 for the third product purchased
    etc etc

Does this make sense?