The Contact added to list trigger lets a contact enter an automation when they are added to a specific list in Brevo. The automation won't be triggered when a contact is moved from one list to another.

You can use this trigger to send a series of welcome emails or onboarding emails.

The Contact is in a segment trigger lets a contact enter an automation when they meet the conditions of a specific segment you've previously created. The automation checks the segment daily at a time of your choosing. Contacts in the segment at this time will enter the automation.

 You can use this trigger to:

• Try to re-engage with inactive contacts and blocklist the ones who aren't interested in your content anymore.
• Send promotional offers to customers who regularly make purchases on your website.
• Remind customers of their upcoming contract or subscription renewal, etc.

The Contact matches custom filters trigger lets a contact enter an automation based on the custom filters you define. The automation checks these filters daily at a time of your choosing. Contacts in who match the filters at this time will enter the automation.

 You can use this trigger to:

• Try to re-engage with inactive contacts and blocklist the ones who aren't interested in your content anymore.
• Send promotional offers to customers who regularly make purchases on your website.
• Remind customers of their upcoming contract or subscription renewal, etc.

The Date in an attribute occurs trigger lets contacts enter the automation when the date stored in a specific date attribute occurs. You can set the automation to trigger on the exact date, before the date, or after the date.

You can use this trigger to send anniversary or birthday emails, as well as contract or subscription renewal reminders.

The Contact submits a form trigger lets a contact enter an automation when they submit a form on your website. This form needs to be created in Brevo. You can choose a specific form name or type (subscription, unsubscription, or update profile form).

You can use this trigger to send a series of welcome emails or onboarding emails.

The Email opened trigger lets a contact enter an automation when they open one of your emails sent from Brevo. It can be an email campaign, a transactional email, or an email sent from an automation. You can specify a specific name or tag for the email.

The Link clicked in an email trigger lets a contact enter an automation when they click a link in an email sent from Brevo. You can specify the email type (email campaign or transactional email), name, and link URL among other filters.

The Unsubscribed from email list trigger lets a contact enter an automation when they unsubcribe from an email list. You can specify information about the email type and name among other filters.

The Cart updated trigger lets a contact enter an automation when they add a product to their cart on your website. You can specify information about the products added to the cart among other filters.

The Order created trigger lets a contact enter an automation when they make a purchase on your website. You can specify information about the products bought and the order amount among other filters.

You can use this trigger to:

• Send a purchase confirmation email.
• Send a "Thank you" email.
• Collect feedback after a purchase.

The Cart deleted trigger lets a contact enter an automation when they remove a product from their cart on your website. You can specify information about the products removed from the cart among other filters.

The Conversation ended trigger lets a contact enter an automation when they end a conversation via email or chat. You can specify the source of the conversation among other filters.

You can use this trigger to send a feedback survey.

The Conversation started trigger lets a contact enter an automation when they start a conversation via email or chat. You can specify the source of the conversation among other filters.

The Message received trigger lets a contact enter an automation every time they receive a message via email or chat. You can specify the source of the message among other filters.

The Deal created trigger lets a contact enter an automation when a deal is created and associated with them. You can specify the deal amount, pipeline, and stage among other filters.

You can use this trigger to send an email with an invitation for a phone, video, or in-person consultation.

The Deal stage updated trigger lets a contact enter an automation when the stage of a deal associated with them is updated. You can specify the deal amount, pipeline, and stage among other filters.

You can use this trigger to send follow-up emails to move the deal to the next stage.

The Task completed trigger lets a contact enter an automation after a task associated with them is marked as done. You can specify the task type, completion date, and due date among other filters.

The Meeting started trigger lets a contact enter an automation when they join a meeting. You can specify the meeting type and URL among other filters.

You can use this trigger to:

• Send a feedback survey to the contact after the meeting has ended.
• Send an email offering relevant upsell or cross-sell opportunities based on the content of the meeting you had with the contact.

The Meeting booked trigger lets a contact enter an automation when they book a meeting. You can specify the meeting type and URL among other filters.

You can use this trigger to:

• Send resources to the contact before the meeting, such as information about your products or services.
• Send a form to the contact to gather relevant information beforehand.

The Meeting canceled trigger lets a contact enter an automation when they cancel a meeting. You can specify the meeting type and URL among other filters.

You can use this trigger to send a new meeting invitation via email.

The Call finished trigger lets a contact enter an automation when they end a call. You can specify the phone line and call type among other filters.

You can use this trigger to send a follow-up email or post-call survey.

The Payment done trigger lets a contact enter an automation when they make a payment using one of your payment links. You can specify the payment link and amount among other filters.

You can use this trigger to:

• Send a "Thank you" email.
• Collect feedback after a purchase.

The Custom event trigger lets a contact enter an automation when they perform a custom event you have created using the "Track" function in the API.

➡️ To learn more about custom events, check our dedicated article Track events.

The Update contact attribute action allows you to update a specific contact attribute with the value of your choice.

The Add contact to a list action allows you to add a contact to a specific list in Brevo.

The Remove contact from a list action allows you to remove a contact from a specific list in Brevo.

The Blocklist a contact action allows you to automatically blocklist a contact from:

• Transactional emails sent by one or more specific senders.
• Email campaigns sent from all senders.

The Assign a user to a contact action allows you to keep track of who is responsible for each of your contacts in Brevo by automatically assigning a user from your organization as their owner. You can assign contacts to either a specific user or distribute them among several specific users using a rotation system.

The Send an email action allows you to send an email to a contact. You can select an existing email template or create a new one. The email can be personalized, such as for birthday or welcome emails.

The Send an SMS action allows you to send either transactional or promotional SMS messages to a contact.

The Send a push notification action allows you to send a push notification to a contact. You can select an existing Wonderpush campaign or create a new one. You can filter the platforms the notification will be sent on and schedule the notification for specific days and times.

The Call a webhook action allows you to receive a notification and include the details of the contact who triggered the event.

The Start another automation action allows you to enroll a contact into a different automation before they continue with the main one. This prevents duplicating steps across multiple automations and ensures each remains focused on its specific objectives.

For example, in an onboarding email series for new customers, after introductory emails, you might offer a demo session. Using the Start another automation action, engaged customers interested in the demo are enrolled in a separate automation focused on demo scheduling, while the main automation exclusively introduces product features.

The Create a task action allows you to automatically generate a task after a specific action is performed. You can predefine the task type, title, due delay and time, owner, and note directly from the automation.

➡️ To learn more, check our dedicated article Create an automation to automatically create tasks.

The Send a wallet notification action allows you to send a push notification to a contact's mobile phone via their Wallet app (Apple Card or Google Wallet). You can also schedule the notification for specific days and times.

The Move to a wallet campaign action allows you to move a contact to a specific campaign. You can also schedule the move for specific days and times.

The Move to a wallet notification and notify action allows you to move a contact to a specific campaign and send a push notification to their mobile phone via their Wallet app (Apple Card or Google Wallet) simultaneously. You can also schedule the move and notification for specific days and times.

The Time delay rule allows you to specify how long a contact will wait before proceeding to the next step of the automation. You can add this rule before any action and add a time delay of # minutes/hours/days/weeks/months to make it seem less automatic and more personalized.

To ensure optimum performance, the minimum delay is 1 minute.

The Conditional split rule allows you to create more complex automations and guide contacts down different paths. You can configure it based on specific events, behaviors, or contact details. Depending on whether contacts meet the condition, they will be follow different paths through your automation.

➡️ To learn more, check our dedicated article Add a conditional split in an automation.

The Wait until an event happens rule allows you to delay an action until a specific event happens. For example, you can choose to wait until a contact is added to a specific list before they proceed through the next steps. You can also set a time limit for how long the contact should wait for the event. If the event does not happen within the specified time, you can decide whether the contact should exit the automation or still proceed through the next steps.