Workflows let you orchestrate multi-channel messaging campaigns that reach users across email, mobile push notifications, and web Flows — all from a single canvas. Set an audience, define a trigger, then build a sequence of messages, logic branches, and time delays that run automatically.

When to use Workflows

Use a Workflow when you need to coordinate more than a single message. Common scenarios:

• Onboarding sequences — welcome a new user with an in-app Flow, then follow up with an email if they haven't completed setup after two days.
• Re-engagement — send a push notification to dormant users, branch based on whether they return, and tailor the next message accordingly.
• NPS follow-ups — trigger different emails for promoters, passives, and detractors using a Multi-path Branch.
• Feature announcements — show an in-app Flow on release day, then send an email recap to anyone who didn't see it.
• Renewal reminders — schedule a timed sequence of emails as a subscription expiration date approaches.

If you only need to show a single in-app experience (a tooltip, a modal, a checklist), you don't need a Workflow — build that directly as a web experience. Workflows are for sequences and cross-channel coordination.

How a Workflow is structured

Every Workflow follows the same pattern: Start → Nodes → Finish.

Start defines who enters the Workflow and what triggers their entry. You choose an audience (one or more segments), then pick a trigger — either "immediately" when a user qualifies, or when a specific event occurs.

Nodes are the steps users pass through. There are three categories:

• Messages — Email, Mobile Push, and Flow. These are the things users actually see. An Email sends an out-of-product message. A Mobile Push sends a notification to the user's device. A Flow shows a web experience (Modal, Slideout, Tooltip) inside your app when the user is next eligible.
• Logic — True/False Branch, Multi-path Branch, Time Delay, and A/B testing. These control the path a user takes. A True/False Branch splits users into two paths based on a condition. A Multi-path Branch splits users across multiple paths based on a user property or segment. A Time Delay pauses progression for a set duration or until a specific date.
• Data — Track Event and Update User Property. These write data back to the user profile or event stream when a user reaches that point in the Workflow, which you can use to trigger other Appcues content or send to external tools.

Finish defines when users exit. You can require them to reach the end of the Workflow, complete a goal, or enter a specific segment. Advanced settings let you configure a timeout threshold, require continued segment membership, and allow re-enrollment.

Prerequisites

Before building your first Workflow, make sure the channels you plan to use are configured:

• Email — Set up your sending domain and physical address in email settings.
• Mobile Push — Connect your apps to the Appcues SDK for push. See push notification settings.
• Web Flows — No additional setup needed beyond having Appcues installed on your site. Flows in Workflows use the same builder and SDK as standalone Flows.

What to read next

Once you're ready to build:

1. Create a Workflow — Set up start criteria, finish criteria, advanced settings, and publish.
2. Add an Email node — Configure sending windows and progression.
3. Add a Mobile Push node — Target by OS, device, and app version.
4. Add a Flow node — Show in-app experiences as part of a Workflow.
5. Add a Multi-path Branch — Route users across multiple paths.

For inspiration, browse the Workflow use cases.