An automation is a series of predefined steps that perform actions based on specific triggers, rules, and actions. You can use automations to handle repetitive tasks in marketing, sales, and contact management, helping you save time, improve efficiency, and reduce manual errors.
For example, this automation sends a welcome email to contacts after they are added to a specific list in Brevo:
|
This article lists all triggers, actions, and rules available in the new automation editor ⬇️:
Triggers
A trigger defines when a contact or custom object record enters an automation. When the conditions of a trigger are met, the contact or record enters the automation and starts moving through the steps.
You can add multiple triggers to a single automation. In this case, a contact or record enters the automation if it meets the conditions of at least one trigger.
Use the following tabs to view the triggers available for contacts or custom object records:
👤 Contacts
The Contact added to list trigger lets a contact enter an automation when they are added to a specific list in Brevo.
Use cases:
-
Welcome emails
Send a welcome email to new subscribers when they join your newsletter or mailing list. -
Promotional campaigns
Send special offers or discount codes to contacts added to a promotional list. -
Onboarding sequences
Trigger onboarding emails or guides when contacts are added to a "new customers" list. -
Double opt-in process for third-party forms
Set up a double opt-in process for a sign-up form created outside of Brevo
The Contact removed from list trigger lets a contact enter an automation when they are removed from a specific list in Brevo.
The Contact matches custom filters trigger lets a contact enter an automation when they match the filter criteria you define directly within the trigger. These filters are not saved anywhere else in your account.
The automation checks the filters at a frequency and time you choose. Any contact who matches the criteria at that moment will enter the automation.
Use cases:
-
Re-engagement campaigns
Re-engage inactive contacts who haven't opened your emails or completed a purchase in a while. -
Promotional offers
Send targeted offers or discount codes to contacts who meet specific purchase or behavior criteria.
The Contact is in a segment trigger lets a contact enter an automation when they meet the conditions of a specific segment. You can select any segment you've already created in your Brevo account.
The automation checks the segment at a frequency and time you choose. Any contact who meets the segment conditions at that moment will enter the automation.
Use cases:
-
Re-engagement campaigns
Re-engage inactive contacts who haven't opened your emails or completed a purchase in a while. -
Promotional offers
Send targeted offers or discount codes to contacts who meet specific purchase or behavior criteria.
The Anniversary trigger lets contacts enter the automation based on a date stored in a date attribute. You can choose to trigger the automation on the exact date, before the date, or after the date.
This trigger ignores the year, so contacts can enter the automation every year on the same date.
Use case:
-
Anniversary or birthday emails
Send personalized emails to contacts on their birthday or the anniversary of a signup or first purchase.
The Contact added manually trigger allows you to manually enroll contacts in an automation from the Contacts page or their details page. This gives you full control over which contacts are included in the automation, regardless of predefined triggers.
➡️ To learn more, check our dedicated article Manually add contacts to an automation.
📄 Forms
The Form submitted 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).
Use cases:
-
Welcome emails
Send a welcome email to new subscribers when they join your newsletter or mailing list. -
Onboarding sequences
Trigger onboarding emails or guides when contacts subscribe through a form.
✉️ Email
The Email opened trigger lets a contact enter an automation when they open one of your emails sent from Brevo. You can apply filters, such as the email name or tag.
Contacts who have activated Apple Mail Privacy Protection (MPP) will be excluded. To learn more, check our dedicated article About Apple Mail Privacy Protection in Brevo.
As of April 2026, the CNIL requires explicit, separate tracking consent before individual email open data can be used to trigger an automation for contacts based in France. If your contacts do not have tracking consent recorded, we recommend replacing this trigger with a consent-independent alternative, such as:
- Email clicked triggers when a contact clicks a link in one of your emails.
- Form submitted triggers when a contact submits a Brevo form.
- Contact matches custom filters triggers based on contact attributes or ecommerce activity (last order date, last click date, etc.).
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 apply filters, such as the email type, name, or link URL.
The Unsubscribed from email list trigger lets a contact enter an automation when they unsubscribe from an email list. You can apply filters, such as the email type or name.
Use case:
-
Sync unsubscribe preferences across email types
Automatically blocklist contacts from email campaigns when they unsubscribe from transactional emails, and vice versa.
🛍️ Ecommerce
The Cart updated trigger lets a contact enter an automation when they add a product to their cart on your website. You can apply filters, such as the name or price of the products added to the cart.
Use cases:
-
Abandoned cart email reminder
Automatically send a reminder email to customers who added products to their cart but did not complete their purchase. -
Multi-touch abandoned cart sequence with coupon codes
Automatically send a multi-channel reminder sequence and offer discounts based on cart value to customers who added products to their cart but did not complete their purchase.
The Cart deleted trigger lets a contact enter an automation when they remove a product from their cart on your website. You can apply filters, such as the name or price of the products removed from the cart.
The Order created trigger lets a contact enter an automation when they make a purchase on your website. You can apply filters, such as the name or price of the products bought or the total order amount.
Use cases:
-
Order confirmation email
Automatically send customers a confirmation with their order details right after purchase. -
Thank-you email
Send a personalized thank-you message to customers after their order to boost engagement and loyalty. -
Post-purchase feedback request
Automatically ask customers for feedback or reviews once their order is completed to gather insights and improve your service.
💬 Conversations
The Sales email clicked trigger lets a contact enter an automation when they click a link in an email sent from a mailbox.
The Sales email opened trigger lets a contact enter an automation when they open an email sent from a mailbox.
The Conversation ended trigger lets a contact enter an automation when their conversation ends. You can apply filters, such as the source of the conversation.
A conversation is considered to have ended based on the following criteria:
-
For emails
The conversation ends 5 minutes after receiving an email. -
For chat and socials
-
If the conversation was not assigned to an agent, or if the agent joined but never replied, it ends 5 minutes after receiving a message.
-
If the conversation was assigned to an agent, it ends as soon as all agents leave the conversation or close the chat, or after 30 minutes of inactivity.
-
The Conversation started trigger lets a contact enter an automation when they start a conversation via email, chat, or socials. You can apply filters, such as the source of the conversation.
The Message received trigger lets a contact enter an automation whenever they send a message via email, chat, or social media. You can apply filters to this trigger, such as the message source.
Use case:
-
Automated replies in Conversations
Automatically send replies for emails and chat messages in Conversations when no agent is available, or to provide an immediate acknowledgment.
- The message is not displayed in Conversations (e.g., if the contact must fill out a form to start the conversation, or if they are banned).
- The message is "echoed" back into Conversations (e.g., if an email is sent from Conversations to an external mailbox connected to Conversations).
💼 Deals
The Deal created trigger lets a contact enter an automation when a deal is created and associated with them. You can apply filters, such as the deal amount, pipeline, or stage.
Use case:
-
Invitation for a phone, video, or in-person consultation
Automatically send new leads an email inviting them to schedule 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 apply filters, such as the deal amount, pipeline, or stage.
Use case:
-
Follow-up emails to advance deals
Automatically send follow-up emails to move a deal to the next stage in your sales process.
The Task completed trigger lets a contact enter an automation after a task associated with them is marked as done. You can apply filters, such as the task type, completion date, or due date.
🤝 Meetings
The Meeting booked trigger lets a contact enter an automation when they book a meeting. You can apply filters, such as the meeting type or URL.
Use cases:
-
Pre-meeting resource emails
Automatically send contacts relevant resources, such as product or service information, before a scheduled meeting. -
Pre-meeting information collection
Send a form to contacts to gather important details ahead of the meeting.
The Meeting started trigger lets a contact enter an automation when they join a meeting. You can apply filters, such as the meeting type or URL.
Use cases:
-
Post-meeting feedback survey
Automatically send a survey to contacts after a meeting to gather their feedback. -
Post-meeting upsell or cross-sell emails
Send emails offering relevant upsell or cross-sell opportunities based on the meeting discussion.
The Meeting canceled trigger lets a contact enter an automation when they cancel a meeting. You can apply filters, such as the meeting type or URL.
Use case:
-
Meeting canceled notification
Automatically send an email to contacts when a scheduled meeting is canceled.
⭐ Loyalty
The Balance minimum value reached trigger lets a contact enter an automation when their loyalty balance reaches the minimum balance limit. You can apply filters, such as the loyalty program or balance name and ID.
The Balance maximum value reached trigger lets a contact enter an automation when their loyalty balance reaches the maximum balance limit. You can apply filters, such as the loyalty program or balance name and ID.
The Balance value updated trigger lets a contact enter an automation when their loyalty balance is updated after earning or redeeming points. You can apply filters, such as the loyalty program, balance name and ID, or transaction type and value.
The Balance value expired trigger lets a contact enter an automation when part of their loyalty balance value expires. You can apply filters, such as the loyalty program, balance name and ID, or expired value.
The Voucher created trigger lets a contact enter an automation when they are assigned a new voucher. You can apply filters, such as the loyalty program, voucher code and ID, or expiration date.
The Voucher redeemed trigger lets a contact enter an automation when they reedeem one of their vouchers. You can apply filters, such as the loyalty program or voucher code and ID.
The Voucher expired trigger lets a contact enter an automation when one of their vouchers reaches its expiration date. You can apply filters, such as the loyalty program or voucher code and ID.
The Voucher revoked trigger lets a contact enter an automation when one of their vouchers is revoked. You can apply filters, such as the loyalty program or voucher code and ID.
The Membership created trigger lets a contact enter an automation when they subscribe to a loyalty program. You can apply filters, such as the loyalty program name and ID.
The Membership year anniversary trigger lets a contact enter an automation every year on their membership subscription anniversary. You can apply filters, such as the loyalty program name and ID or subscription date.
The Membership Revoked trigger lets a contact enter an automation when they unsubscribe from or are deleted from a loyalty program. You can apply filters, such as the loyalty program name and ID.
The Tier association updated trigger lets a contact enter an automation when their subscription tier changes (e.g., from Bronze to Silver). You can apply filters, such as the loyalty program name and ID.
📞 Phone
The Call finished trigger lets a contact enter an automation when they end a call. You can apply filters, such as the phone line or call type.
You can use this trigger to send a follow-up email or post-call survey.
💰 Payment
The Payment request created trigger lets a contact enter an automation when you create a payment request associated with them.
➡️ To learn more, check our dedicated article Send payment requests to your clients.
The Payment request reminder sent trigger lets a contact enter an automation when you send them a payment request reminder.
➡️ To learn more, check our dedicated article Send payment requests to your clients.
The Payment done trigger lets a contact enter an automation when they make a payment using one of your payment links or requests. You can apply filters, such as the payment link or amount.
You can use this trigger to send a "Thank you" email or collect feedback after a purchase.
🔔 Push notifications
The Session started trigger lets contacts enter an automation when they open your website or mobile app for the first time or after 30 minutes of inactivity if they've already had it open. You can apply filters, such as the attribution reason, campaign ID, or notification ID.
The Push notification clicked lets contacts enter an automation when they click one of your push notifications. You can apply filters, such as the attribution reason, campaign ID, or notification ID.
The Subscribed to push notifications lets contacts enter an automation when they subscribe to receive your push notifications. You can specify the following subtypes:
- Soft: The user has temporarily disabled the display of push notifications.
- New: The user has subscribed to receive your push notifications for the first time.
The Unsubscribed from push notifications lets contacts enter an automation when they unsubscribe from your push notifications and stop receiving them. You can specify the following subtypes:
- Invalidated: The user's device has been permanently flagged as unsubscribed by Google or Apple.
- Soft: The user has temporarily disabled the display of push notifications on their device.
💳 Wallet
The Pass installed lets contacts enter an automation when they add a pass to their mobile wallet app.
You can use this trigger to:
- Send a confirmation message after a pass is installed.
- Start a follow-up sequence.
The Pass downloaded lets contacts enter an automation when they download a pass to their device by clicking the link provided.
You can use this trigger to remind the contact to download a pass if they haven't done so yet.
The Optin updated lets contacts enter an automation when a pass is installed or deleted.
The Status changed trigger lets contacts enter an automation when they install or delete a pass and their owner status is updated.
The Enrolled lets contacts enter an automation when they install their first pass.
The Pass status changed lets contacts enter an automation when the status of one of their wallet pass is updated, such as when it's used, expired, or canceled.
The Anonymized lets contacts enter an automation when you anonymize them.
The Redeem failed trigger lets contacts enter an automation when they try to redeem a link but the redemption fails (for example, if the code entered is invalid or expired).
The Redeem success trigger lets contacts enter an automation when they successfully redeem a link (the code entered is valid).
The Counter value changed trigger lets contacts enter an automation when the value of a counter linked to their profile changes (for example, a balance counter).
🔔 Web Push
The Subscriber deactivated lets contacts enter an automation when they are no longer reachable (e.g., the device was reset, notifications were disabled, or the subscription expired). You can apply filters, such as the subscriber's country or device.
The Subscriber refreshed lets contacts enter an automation when their browser updates their push subscription details. You can apply filters, such as the subscriber's country or device.
The Webpush delivered lets contacts enter an automation when they receive a web push notification. You can apply filters, such as the subscriber's country or the campaign ID.
The Webpush clicked lets contacts enter an automation when they click one of your web push notifications. You can apply filters, such as the subscriber's country or the campaign ID.
The Webpush closed lets contacts enter an automation when they close one of your web push notifications. You can apply filters, such as the subscriber's country or the campaign ID.
The Subscriber added lets contacts enter an automation when they subscribe to your push notifications and are added to your contacts. You can apply filters, such as the subscriber's country or device.
🖥️ Website
The Webpage visited trigger lets a contact enter an automation when they visit a page on your website. You can apply filters, such as the webpage name or URL.
Use cases:
-
Page visit follow-up emails
Automatically send follow-up emails when a contact visits a specific page on your website.
The WhatsApp reply received lets contacts enter an automation when they reply to a WhatsApp campaign. You can apply filters, such as the campaign name, button, or content of the contact's reply.
Use cases:
-
Keyword-based responses
Automatically send a WhatsApp template in response to specific keywords (e.g., "YES", "Pricing", "Demo").
⚡ Custom
Custom event triggers let a contact enter an automation when they perform a specific action that you have defined and tracked using a custom event.
➡️ To learn more about custom events, check our dedicated article Create custom events in Brevo.
The Based on a date attribute trigger lets custom object records enter the automation based on a date stored in a date attribute. You can choose to trigger the automation on the exact date, before the date, or after the date.
This trigger takes the year into account, so records only enter the automation on the specified date.
You can also filter this trigger using information from the contact associated with the record.
Use case:
-
Automated reminders for dates stored in your custom objects
Automatically send reminders to customers about upcoming renewals or deadlines, keeping them engaged and reducing manual follow-ups.
The [Record] created trigger lets custom object records enter the automation when they are created. You can also filter this trigger using information from the contact associated with the record.
The [Record] updated trigger lets custom object records enter the automation when one of their attributes is updated. You can also filter this trigger using information from the contact associated with the record.
Custom event triggers let a custom object record enter an automation when they perform a specific action that you have defined and tracked using a custom event.
➡️ To learn more about custom events, check our dedicated article Create custom events in Brevo.
Actions
An action defines what happens to a contact or custom object record in an automation. When a contact or record meets a trigger or rule, the action is executed. Actions can include tasks like sending emails, updating contact information, or adding contacts to lists.
👤 Contacts
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 Update contact attribute action allows you to update or delete the value of a specific contact attribute for a contact.
The Blocklist 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.
You can use this action to automatically blocklist contacts from email campaigns when they unsubscribe from transactional emails, and vice versa.
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.
➡️ To learn more, check our dedicated article Assign an owner to your contacts manually or automatically.
The Delete a contact action allows you to automatically delete a contact if they meet certain criteria. For example, you may want to automatically delete contacts that have not interacted with you in a long time.
➡️ To learn more, check our dedicated article Delete contacts.
The Update company attribute action allows you to update a specific company attribute with the value of your choice.
✉️ Messaging
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.
➡️ To learn more, check our dedicated article Send an email from an automation.
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 on which the notification will be sent and schedule the notification for specific days and times.
The Send a one-to-one email from a mailbox action allows you to reply to an email using the same mailbox it was originally received in. You can choose the mailbox, customize the subject line and message content, and schedule the email to be sent on specific days and at specific times.
The Send a WhatsApp message action allows you to automate the sending of WhatsApp messages to your contacts. You can only select WhatsApp templates that have already been approved by Meta. Your WhatsApp messages can be personalized, such as birthday or welcome emails.
➡️ To learn more, check our dedicated article Send WhatsApp messages through an automation.
The Notify by email action allows you to send internal notifications to specific contacts or to recipients defined in contact attributes. You can use an existing template created with the simple editor or write new content directly in the automation editor.
➡️ To learn more, check our dedicated article Receive an email notification when a form is submitted.
🔗 Webhooks
The Call a webhook action allows you to create an outbound webhook from an automation to send a real-time notification with event data from Brevo to an external app when a contact reaches this step. You can also choose to include contact details in the notification.
➡️ To learn more, check our dedicated article Send outbound webhooks from an automation.
💼 Deals
The Create a task action allows you to automatically generate a task after a specific action is performed. You can define 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 Update deal attribute action allows you to update a specific deal attribute with the value of your choice. You can choose to update the attribute of a contact’s:
|
|
The Duplicate a deal action allows you to automatically duplicate the most recent deal associated with a contact. All deal attributes, notes, and associated objects are replicated in the new deal. You can define the deal pipeline and stage, and even add a prefix to better identify deals duplicated through this action.
You can use this action to re-create lost deals, giving you another opportunity to win them back.
The Create a deal action allows you to automatically generate a deal after a specific action is performed. You can define the deal pipeline, stage, name prefix, owner, and follow-up task. Additionally, the deal can be assigned to an owner using a rotation system.
➡️ To learn more, check our dedicated article Create an automation to automatically create deals.
↪️ Automations
The Start another automation action allows you to enroll a contact into a different automation before they continue in the current one. You can choose the exact step in the other automation where the contact will enter. This helps avoid duplicating steps across automations and keeps each workflow focused on its specific purpose.
For example, in an onboarding email series for new customers, you might offer a demo session after introductory emails. 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 Redirect contact to another step action allows you to move a contact directly to a different step within the same automation. After being redirected, the contact will continue through the automation from the selected step.
💳 Wallet
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 choose to 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.
Rules
A rule defines the condition a contact or custom object record must meet to move to the next step in an automation. Rules let you adjust the flow based on behaviors, events, or contact details.
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.
➡️ To learn more, check our dedicated article Differences between Time delay and Wait until an event happens.
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 follow different paths through your automation.
➡️ To learn more, check our dedicated article Add a conditional split to an automation based on contact details and behavior.
The Percentage split rule allows you to A/B test different paths or distribute contacts between two branches of an automation. When a contact reaches a percentage split, they will be randomly assigned to one of the two branches based on the specified percentages.
➡️ To learn more, check our dedicated article Add a percentage split to an automation for A/B testing and random distribution.
The Wait until an event happens rule allows you to delay an action until a specific event happens. For example, you can 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, the contact will proceed to the "No" branch.
➡️ To learn more, check our dedicated article Differences between Time delay and Wait until an event happens.
⏭️ What's next?
- Overview of the new automation editor
- Use a trigger to start an automation
- Define and manage the audience entry and exit conditions for an automation
🤔 Have a question?
If you have a question, feel free to contact our support team by creating a ticket from your account. If you don't have an account yet, you can contact us here.
If you’re looking for help with a project using Brevo, we can match you with the right certified Brevo Agency partner.