Skip to main content

Building Automations

Create automated workflows with triggers, actions, conditions, and delays.

Matt Thomas avatar
Written by Matt Thomas
Updated this week

Automations let you create powerful workflows that run automatically when specific events happen. Instead of manually performing repetitive tasks, you can set up automations to handle them for you — from welcoming new members to rewarding loyal customers.


Getting Started

Navigate to Engage > Automations in your dashboard to access the automations page.

Note: Automations are a PRO/Engage feature. You'll need an active Engage subscription to create and run automations.


The Automations List

The automations list page shows all of your automations at a glance. For each automation, you'll see:

  • Name — the name you gave the automation

  • Trigger type — what event starts the automation (e.g., signup, birthday, order received)

  • Status toggle — whether the automation is currently enabled or disabled

Use this page to quickly monitor and manage all your workflows in one place.


Creating a New Automation

Click the Create Automation button to get started. You have two options:

  • From scratch — build a brand-new automation with a blank canvas

  • From template — choose a pre-built template to get started quickly and customize it to your needs


The Visual Automation Builder

The automation builder uses a visual flow diagram where each step is represented as a connected node. You'll build your automation by adding and connecting nodes in sequence:

  1. Trigger node — the starting point that fires when a specific event occurs

  2. Condition nodes (optional) — if/else branches that check member attributes before continuing

  3. Action nodes — the tasks that get executed (give credit, send notification, add tag, etc.)

  4. Delay nodes (optional) — pause the flow for a set duration before continuing

Drag, drop, and connect nodes to design your workflow visually. The flow diagram makes it easy to see exactly what will happen and in what order.


How Automations Work

When an automation runs, it follows this sequence:

  1. Trigger fires — the specified event occurs (e.g., a new member signs up)

  2. Conditions checked — any conditions are evaluated to determine which path to follow

  3. Actions executed — the actions in the flow are carried out in order, respecting any delays between them

Each automation runs independently for each member who matches the trigger. If 10 members sign up, the automation runs 10 separate times.


Enabling and Disabling Automations

Use the status toggle on the automations list page or within the builder to enable or disable an automation at any time.

  • Enabled — the automation is live and will fire when its trigger conditions are met

  • Disabled — the automation is paused and will not fire, even if the trigger event occurs

Disabling an automation does not delete it. You can re-enable it whenever you're ready.


Testing Automations

Before enabling an automation for all members, test it thoroughly:

  • Create a test member in your account

  • Enable the automation and trigger the event for your test member

  • Verify that each action executes as expected

  • Check the execution history for any errors


Execution History and Status Monitoring

Each automation tracks its execution history so you can monitor performance and troubleshoot issues. You'll see:

  • When the automation was triggered

  • Which member triggered it

  • Whether each step completed successfully or encountered an error

  • The current status of in-progress automations (e.g., waiting on a delay)

Use execution history to verify your automations are working correctly and to diagnose any problems.


Tips

  • Start simple — create a basic automation first, then add conditions and delays as needed

  • Use descriptive names so you can quickly identify each automation in the list

  • Always test with a test member before enabling for your full audience

  • Use delays strategically — for example, wait 24 hours after signup before sending a follow-up notification

  • Review execution history regularly to catch and fix any issues early

  • Combine automations with other Engage features for maximum impact

Did this answer your question?