Workflows
Workflows are under development and coming soon. The features described in this section aren't generally available yet, and details may change before launch.
A workflow reacts to an event. When a member does something, such as making a purchase, starting a checkout, or signing up, the workflow starts a run for that member and walks them through a series of steps you build: wait a while, check something about them, wait for another event, send an email, add them to a segment, or set a user attribute.
Use workflows for things like:
| Use | How it's built |
|---|---|
| Post-purchase email | Trigger on purchase, then send a thank-you or receipt email. |
| Abandoned checkout | Trigger on begin_checkout, wait up to an hour for purchase. If it never comes, send a reminder email. |
| Drip campaign | Trigger on sign_up, then send an email, wait two days, send another, and so on. Set purchase as the exit event so the drip stops once the member buys. |
| Glue automation | Trigger on a platform event such as audience_member.created and add the member to a segment or set a user attribute, with no code. |
Workflows are off by default. Once they're turned on for your organization, Workflows appears in the sidebar, along with its Emails and Topics pages, a Workflows page under Organization Settings, and Workflows and Email tabs on each audience member. Contact your Allegro administrator to have it turned on.
How a workflow works
| Term | Meaning |
|---|---|
| Trigger | The event that starts the workflow for a member, with optional conditions. See Which events can trigger a workflow. |
| Step | One box on the canvas: a condition, a delay, a wait for an event, an action, or an end. See Building a workflow. |
| Run | One member going through the workflow. Every run is recorded step by step. See Runs. |
| Version | A snapshot taken each time you publish. A run follows the version that was live when it started, even if you publish changes while it's running. |
A run always belongs to a known audience member. An event that arrives without a member counts for whoever is signed in on the device that sent it. Events from anonymous visitors don't start or move runs.
The Workflows list
Go to Workflows in the sidebar to see every workflow. Use the All, Drafts, Published, and Archived tabs and the search box to narrow the list. Each row shows:
| Column | Shows |
|---|---|
| Workflow | The workflow's name. |
| Trigger | The event that starts it. |
| Status | Draft, Published, or Archived. |
| Active runs | How many members are in the workflow right now. |
| Runs · 7d | How many runs started in the last seven days. |
| Last run | When the most recent run started. |
| Updated | When the workflow was last saved. |
Each row's menu offers Edit, Runs, Duplicate, and Archive. Archived workflows offer Restore, which brings the workflow back as a draft.
Quick start
- Go to Workflows and click New workflow.
- Click the Trigger card and choose the event that starts the workflow.
- Click the + under the trigger to add steps.
- Open Settings to choose which properties it runs on and how often a member can enroll.
- Open Test and run it for one member to check the path it takes.
- Click Save & publish.
Each step is covered in detail in Building a workflow.
Limits
| Limit | Value |
|---|---|
| Published workflows per organization | 100 |
| Steps in one workflow | 50 |
| Nesting depth (paths inside paths) | 8 levels |
| Steps a single run can execute | 200 |
| Delays, wait timeouts, and segment expiry | 1 minute–90 days |
| Occurrences a wait can count | 1–100 |
Allegro checks for due delays and timeouts once a minute, so a step set to wait one hour continues about an hour later, not to the second.
Managing workflows with AI clients
Everything on these pages can also be done through Allegro's MCP server: build and publish workflows, dry run them, read and cancel runs, and manage workflow emails, topics, and opt-outs. See the workflow tools in the MCP Server guide.