Triggers

Learn about the different trigger types available for starting your automations

What are Triggers?

Triggers are the starting point of every automation. They determine when and how contacts enter your automated email sequence.

Trigger types

Brew supports four trigger types to start your automations:

Triggered when a new contact is added to your audience.

Perfect for:

• Welcome sequences
• Onboarding email series
• First-time user guides

Triggered when a new contact is added to your audience.

Perfect for:

• Welcome sequences
• Onboarding email series
• First-time user guides

Triggered when a contact is added to a specific subscription group.

Perfect for:

• Segment-specific welcome emails
• Topic-based educational series
• Special offer sequences

Triggered when a contact’s property changes.

Perfect for:

• Status change follow-ups
• Engagement-based sequences
• Profile completion reminders

Triggered when a specific event occurs via API or integration.

Perfect for:

• Purchase confirmations
• Abandoned cart recovery
• Feature usage milestones

Working with the Event received trigger

The “Event received” trigger is especially powerful as it allows you to integrate Brew with your product, website, or other systems to create behavior-based email sequences.

About events

Events represent a payload of data sent to Brew that can trigger automations. They contain personalized data that can be used in your emails.

Creating events

Events can be created in several ways:

1. Automatically by sending an event
   • Send a new event name via API to create it automatically
2. Manually from the Triggers page
   • Navigate to Settings → Triggers to create events manually
3. From the automation builder
   • When creating an automation, select “Event received” as the trigger type
   • Enter a new event name or select an existing one

Sending events via API

Use Brew’s API to send events:

{
  "email": "[e-mail]",
  "eventName": "planUpgrade"
}

The eventName can be an existing event in your account or a new one.

If a contact with the provided email doesn’t exist, a new contact will be created.

Using trigger properties

You can include additional data with each event using trigger properties. These properties allow you to personalize emails based on event-specific information.

Adding trigger properties

You can add trigger properties in two ways:

1. From the Triggers page
   • Navigate to Settings → Triggers
   • Click on an event
   • Click ”+ Add trigger property”
2. From the automation builder
   • When creating an automation with an “Event received” trigger
   • Click “Edit trigger properties”

Types of trigger properties

Trigger properties can be one of four types:

• String: Text values
• Number: Numeric values
• Boolean: True/false values
• Date: Date and time values (Unix timestamp in milliseconds or ECMA-262 date-time string)

All property names must be unique within the same event, and spaces are trimmed from the beginning and end of property names.

Sending trigger properties

Include trigger properties in your API request using eventProperties:

{
  "email": "[e-mail]",
  "eventName": "planUpgrade",
  "firstName": "Sam",
  "eventProperties": {
    "newPlan": "Pro",
    "oldPlan": "Basic",
    "planPrice": 29,
    "isLifetime": false,
    "updateDate": "2024-03-07T10:09:23Z"
  }
}

Important notes:

• Brew attempts to convert mismatched types
• New properties not previously defined won’t be available for use in emails
• Always define trigger properties before sending them in events

Using trigger properties in emails

Once defined and sent, trigger properties become available in your emails:

1. In the email editor, click the Trigger properties icon (⚡️) in the toolbar
2. Select the property you want to add
3. The property will be inserted as a variable that gets replaced with the actual value when the email is sent

This allows you to create highly personalized emails based on the specific event data.

Testing triggers

You can test your trigger setup without sending actual emails:

1. Use test contacts with appropriate properties
2. Monitor how they move through your automation
3. For the “Event received” trigger, you can send test events via the API
4. View event logs in Settings → Triggers to confirm your events are being properly received

Trigger best practices

Choose the right trigger for your goal

Match your trigger to your automation’s purpose:

• For new users → Contact added
• For segment-specific content → Added to List
• For behavior-based journeys → Contact updated
• For app/website interactions → Event received

Specify trigger frequency

Decide how often contacts should enter your automation:

• One time: Contact enters only the first time they meet the trigger condition
• Every time: Contact enters each time they meet the trigger condition

For example, use “One time” for welcome sequences and “Every time” for purchase confirmations.

Use data enrichment with triggers

Combine triggers with audience filters for more precise targeting:

• Start with a broader trigger
• Add audience filters immediately after to refine who continues
• Example: Trigger on “Contact added” but filter to show content only to specific segments

Need help choosing the right trigger? Simply describe your goal to Brew, and it will suggest the most appropriate trigger type and configuration.

Back to Automations

Return to the main Automations page

Set up Branching

Learn how to create personalized paths after your trigger