Triggers
Triggers are automation rules that execute actions when specific events occur. They enable you to automate repetitive tasks like starting drip campaigns, sending notifications, or updating contact data without manual intervention.
Overview
A trigger consists of three components:
+-------------+ +-------------+ +-------------+
| EVENT | --> | TIMING | --> | ACTION |
| (When) | | (Delay) | | (What) |
+-------------+ +-------------+ +-------------+
Examples:
- Contact added to list --> Instantly --> Start drip group
- Field value changed --> After 1 hour --> Send notification
- Added to segment --> After 3 days --> Move to another list
Viewing Triggers
Navigate to Actions → Triggers to view all triggers.
Page Features
- Add New button to create a trigger
- Pre-Defined Templates button for template triggers
- Bulk Actions dropdown for operations on selected items
- Drag handle (≡) to reorder triggers by dragging
Instant contact-based triggers (contact added, field changed) execute in real-time - immediately when the event occurs.
Delayed triggers and segment-based triggers are processed by a cron job at regular intervals. A note at the top shows "The triggers are set to run every X minutes. You can change this on the Cron Settings page." For these triggers, the maximum delay equals the cron interval.
Triggers can be reordered by dragging - they process in the order shown.
Trigger Information
| Column | Description |
|---|---|
| Name | Trigger name |
| Status | Toggle switch to enable/disable |
| Last Activity | When the trigger last executed |
| Created On | Date and time created |
| Actions Performed | Number of times the trigger has executed |
| Actions | Edit and Delete icons |
Creating a Trigger
Navigate to Actions → Triggers and click Add New. The trigger creation wizard has two steps.
Step 1: Event
Define when the trigger should fire.
Status
Toggle to enable or disable the trigger immediately upon creation.
Trigger Name
Enter a descriptive name for the trigger (required).
Best practices:
- Include the purpose: "Welcome Series Trigger"
- Be specific: "API Signup - Start Onboarding"
Description
Optional field to describe what this trigger does. Useful for documentation and team collaboration.
Event
Select the event that activates this trigger:
| Event | Description |
|---|---|
| Contact is added to a list | Fires when a contact joins a list |
| Contact is added to a segment | Fires when a contact qualifies for a segment |
| When a field value is changed | Fires when a custom field is updated |
Event: Contact is Added to a List
Triggered when a contact is added to one or more lists.
Adding Method
Select how the contact must be added to trigger the action:
| Method | Description |
|---|---|
| Apply all | Any adding method triggers the action |
| Manual | Contact added through the UI |
| API | Contact added via API call |
| Import | Contact added through CSV import |
| Webform | Contact added through a subscription form |
List Selection
Choose which lists activate this trigger:
| Option | Description |
|---|---|
| Selected lists | Only specific lists you choose |
| Any list | All lists trigger the action |
When Selected lists is chosen:
- A searchable tree structure displays all lists organized by groups
- Check individual lists or entire groups
- Lists show contact count in parentheses (e.g., "Newsletter (500)")
- Use Filter Checked toggle to show only selected lists
Lists without a configured sending domain show a "MISSING SENDING DOMAIN" warning with a "Fix now" link. Configure the sending domain before using the list in triggers.
Click Continue to proceed to Step 2.
Event: Contact is Added to a Segment
Triggered when a contact qualifies for a dynamic segment.
Segment Selection
Choose which segments activate this trigger:
| Option | Description |
|---|---|
| Selected segments | Only specific segments you choose |
| Any segment | All segments trigger the action |
Click Continue to proceed to Step 2.
Event: When a Field Value is Changed
Triggered when a custom field value is updated.
Field Selection
| Option | Description |
|---|---|
| Any field | Any field change triggers the action |
| Selected field | Only changes to a specific field |
When Selected field is chosen, select the field from the dropdown (e.g., First Name, Company, etc.).
Value Condition
| Option | Description |
|---|---|
| Changed to any value | Any new value triggers the action |
| Changed to this value | Only a specific value triggers the action |
When Changed to this value is chosen, enter the exact value that must be set.
Click Continue to proceed to Step 2.
Step 2: Action
Define what happens when the trigger fires.
When to Execute
Choose when the action should run after the triggering event:
| Option | Description |
|---|---|
| Instantly | For contact-based triggers (contact added, field changed): executes immediately in real-time. For segment-based triggers: executes at the next cron cycle. |
| After some time | Execute after a specified delay from the event time (processed by cron) |
Contact-based triggers set to Instantly execute the moment the event occurs - no waiting for cron. This is ideal for welcome emails, instant notifications, and real-time responses.
Delay Settings (After some time)
| Field | Description |
|---|---|
| Duration | Numeric value (e.g., 5, 30, 1) |
| Unit | Minutes, Hours, Days, Weeks, Months, Years |
Examples:
- 10 Minutes after contact added - Quick follow-up
- 1 Hour after signup - Allow time to complete profile
- 3 Days after email opened - Engagement follow-up
- 1 Week after last activity - Re-engagement prompt
How delayed timing works: The system calculates when a contact qualifies based on the event time plus your delay. For example, if a contact is added at 2:00 PM and the delay is 30 minutes, they qualify at 2:30 PM. The action executes at the next cron run after 2:30 PM. With a 15-minute cron interval, the maximum additional delay is 15 minutes.
Action to Perform
Select the action from the dropdown:
| Action | Description |
|---|---|
| Send a broadcast | Send an email campaign |
| Send a notification email to admin | Alert an administrator |
| Start a drip group | Begin an autoresponder sequence |
| Change status to active or inactive | Update contact status |
| Change format to receive HTML or Text | Set email format preference |
| Update a custom field value | Modify contact data |
| Move contact to another list | Transfer to different list |
| Copy contact to another list | Duplicate to another list |
| Delete the contact | Remove from system |
| Add contact to suppression list | Block future emails |
Action: Send a Broadcast
Send an email campaign to the contact.
Settings
Select Broadcast
Choose the broadcast to send from the dropdown.
Sending Node
Select SMTP servers for delivery. Nodes are organized in a tree structure by groups:
- Check entire groups to use all nodes in the group
- Check individual nodes for specific selection
Sender Information
Choose how sender details are determined:
| Option | Description |
|---|---|
| From Contact List | Use sender info from the contact's list |
| From Sending Node | Use sender info from the SMTP node |
| Custom | Enter custom sender details |
When From Sending Node is selected:
- Use the Sender Name as defined in the sending node - Checkbox to use node's default name
- Sender Name - Override field (optional)
Options
| Toggle | Description |
|---|---|
| Track Opens | Enable open tracking |
| Track Clicks | Enable click tracking |
| Skip Duplicates | Don't send if contact already received this broadcast |
| Insert Unsubscribe Link | Add unsubscribe link to email |
| Skip unconfirmed | Don't send to unconfirmed contacts |
Click Submit to save the trigger, or Back to return to Step 1.
Action: Send a Notification Email to Admin
Send an email notification to an administrator or team member.
Settings
| Field | Description |
|---|---|
| Recipient Email | Email address to receive notification |
| Subject | Notification email subject |
| Content | HTML content of the notification |
| Sending Node | SMTP server for delivery |
Action: Start a Drip Group
Begin an autoresponder/drip campaign for the contact.
Settings
| Field | Description |
|---|---|
| Drip Group | Select the drip campaign to start |
Action: Change Status to Active or Inactive
Update the contact's status.
Settings
| Option | Description |
|---|---|
| Active | Contact can receive emails |
| Inactive | Contact is paused from receiving emails |
Action: Change Format to Receive HTML or Text
Update the contact's preferred email format.
Settings
| Option | Description |
|---|---|
| HTML | Receive HTML formatted emails |
| Text | Receive plain text emails |
Action: Update a Custom Field Value
Change a custom field value for the contact.
Settings
| Field | Description |
|---|---|
| Custom Field | Select the field to update |
| New Value | Value to set |
Action: Move Contact to Another List
Move the contact to a different list (removes from source list).
Settings
| Field | Description |
|---|---|
| Target List | List to move contact to |
| Duplicate Handling | How to handle if contact exists in target |
Duplicate Handling Options
| Option | Description |
|---|---|
| Skip & Keep Original | Don't move if exists in target, keep in source |
| Skip & Remove Original | Don't move if exists in target, remove from source |
| Overwrite | Move and overwrite existing record in target |
Action: Copy Contact to Another List
Copy the contact to another list while keeping the original.
Settings
| Field | Description |
|---|---|
| Target List | List to copy contact to |
| Duplicate Handling | How to handle if contact exists in target |
Action: Delete the Contact
Remove the contact from the system.
This action permanently removes the contact and cannot be undone.
Action: Add Contact to Suppression List
Add the contact to a suppression list to prevent future emails.
Settings
| Option | Description |
|---|---|
| Global Suppression | Suppress across all lists |
| List Suppression | Suppress only in specific list |
Pre-Defined Templates
Mumara provides trigger templates that you can clone to your account.
Accessing Templates
- Navigate to Actions → Triggers
- Click Pre-Defined Templates
- Browse available templates
- Click Clone to copy a template
Cloning Templates
Clone Single Template:
- Click the Clone button next to any template
- The template is copied to your triggers list
- Edit and customize as needed
Clone All Templates:
- Click Clone All to copy all available templates
- All templates are added to your triggers list
Managing Triggers
Editing a Trigger
- Click the Edit icon next to a trigger
- Modify settings in Step 1 (Event) or Step 2 (Action)
- Click Submit to save changes
Reordering Triggers
- Click and hold the drag handle (≡) on the left of a trigger
- Drag to the desired position
- Release to save the new order
Triggers execute in the order shown in the list.
Deleting Triggers
Single Deletion:
- Click the Delete icon (trash) next to a trigger
- Confirm deletion
Bulk Deletion:
- Select multiple triggers using checkboxes
- Choose Delete selected from Bulk Actions
- Confirm deletion
Changing Status
Toggle the Status switch directly in the trigger list to enable or disable a trigger.
Trigger Limits
Triggers may have action limits based on your package or user settings.
Monthly Action Limits
- Each trigger execution counts toward your monthly limit
- When limit is reached, triggers are automatically disabled
- Triggers re-enable when the limit resets (monthly)
Monitoring Usage
- View Actions Performed column in trigger list
- Check notifications for limit warnings
- Contact administrator if you need higher limits
Auto-Disable Reasons
| Reason | Description | Resolution |
|---|---|---|
| Limit Reached | Monthly action limit exceeded | Wait for reset or increase limit |
| List Blocked | Associated list is blocked | Unblock the list or change trigger lists |
Best Practices
Trigger Design
- One trigger per purpose - Don't overload a single trigger
- Test first - Use test contacts before enabling for production
- Monitor performance - Check action counts and adjust as needed
- Use descriptions - Document what each trigger does
Avoiding Common Issues
Trigger Loops:
BAD: Trigger A updates field --> Trigger B fires on field change --> Trigger A fires
To avoid loops:
- Don't create triggers that can activate each other
- Use "Changed to this value" rather than "Changed to any value"
- Consider timing delays to break potential loops
Over-triggering:
- Target specific lists instead of "Any list"
- Use specific adding methods when appropriate
- Use "Changed to this value" for precise targeting
Performance Tips
- Order matters - Arrange triggers by priority using drag-and-drop
- Use delays wisely - A 10-minute delay works just as well as "Instantly" for most use cases
- Clean up unused triggers - Delete or disable inactive triggers
- Review periodically - Audit triggers monthly
Timing vs Resources
The trigger cron interval determines both precision and server load:
| Interval | Precision | Server Load | Recommended For |
|---|---|---|---|
| 1 minute | High | Heavy | Time-critical automations only |
| 5 minutes | Good | Moderate | Balanced approach |
| 15 minutes | Standard | Light | Most marketing automations |
For most email marketing automations (welcome series, follow-ups, re-engagement), a 15-minute interval is sufficient. Reserve 1-minute intervals for time-sensitive triggers like abandoned cart recovery or real-time alerts.
Troubleshooting
Trigger Not Firing
Possible causes:
- Trigger status is disabled
- Event doesn't match criteria
- Contact doesn't meet conditions
- Monthly limit reached
Solutions:
- Check trigger status toggle is enabled
- Verify event settings match the actual event
- Review contact data
- Check Actions Performed count
Action Not Executing
Possible causes:
- Missing required entities (broadcast, drip, SMTP)
- Insufficient permissions
- Invalid configuration
Solutions:
- Verify all selected items exist
- Check user permissions
- Review action settings
Trigger Auto-Disabled
Possible causes:
- Monthly action limit reached
- Associated list is blocked
Solutions:
- Wait for monthly limit reset
- Request limit increase
- Unblock associated lists
- Check notifications for specific reason
Actions Seem Delayed
Understanding trigger timing:
Triggers are time-based, not real-time. The system evaluates qualifying contacts at each cron interval, so the maximum delay equals your cron interval. This is normal behavior.
Example: Trigger set to "10 minutes after contact added" with 15-minute cron interval:
- Contact added at 2:01 PM → qualifies at 2:11 PM
- Cron runs at 2:00 PM, then 2:15 PM
- Action executes at 2:15 PM (4 minutes after qualifying time)
If actions aren't running at all:
- Verify the trigger cron job is running (check cron logs)
- Ensure trigger status is enabled
- Check if trigger hit its monthly action limit
- Verify the trigger conditions match the actual events
Solutions:
- Check cron settings (note shows frequency at top of page)
- For more precise timing, reduce cron interval (increases server load)
- Contact administrator to verify cron status
Next Steps
- Webhooks - Set up real-time event notifications
- Drip Campaigns - Create email sequences for triggers
- Segments - Build segments to use with triggers