A Flow node qualifies a user to see a web Flow when they reach that point in the Workflow. This doesn't guarantee they'll see it immediately — they need to be logged into your app and match the triggering and URL conditions — but it means they're eligible. You can require that they see or complete the Flow before progressing further in the Workflow.

No additional setup is needed beyond having Appcues installed on your site. Flows in Workflows use the same builder and SDK as standalone Flows.

Localized Flows are not supported in Workflows. If you need to show different language versions, create separate Flow nodes for each locale and use a Multi-path Branch or True/False Branch to route users based on a language user property.

Add a Flow to the canvas

1. Click any + button on the Workflow canvas.
2. Under Messages, select Flow.

1. Enter a name and a Build URL. The Build URL is a page in your app where you can open the Flow in the Appcues Builder to edit it. This doesn't have to be the same URL where the live Flow will appear.
2. Choose Create to build a new Flow from scratch, or Copy to duplicate an existing Flow.

• Copy opens a search modal where you select the source Flow. The copy is independent — edits won't affect the original.
• Create opens the Appcues Builder so you can build the Flow's content directly.

5. Once created, the Flow sidebar opens on the canvas. From here you manage settings and can return to the Builder to edit content.

When can users move to the next node?

This setting controls what must happen before the user progresses past the Flow node. The options:

• Shown — The user moves forward once the Flow has been displayed to them.
• Completed — The user moves forward once they finish every step of the Flow.

For either option, you can set a Maximum wait so users eventually progress even if they don't see or complete the Flow. This prevents users from getting stuck indefinitely at a Flow node.

Flow triggering

• Show immediately — The Flow appears as soon as the user loads a matching page while they're eligible.
• When an event occurs — The Flow appears when the user triggers a specific event. Configure this with event triggering.

You cannot manually trigger a Flow that is inside a Workflow.

Frequency

• Show Once — The user sees the Flow a single time. This is the typical choice for onboarding or announcements.
• Show Every Time — The user sees the Flow each time they match the trigger conditions, for as long as they're enrolled in the Workflow. Once they exit the Workflow, the Flow stops appearing.

For details on how frequency works, see Setting up Flow Frequency.

URL targeting

By default, the Flow can appear on any page. To restrict it:

1. Select At a specific path.
2. Click the edit button to open the conditions editor.
3. Define the URL conditions where the Flow should (or shouldn't) appear.
4. For details on URL conditions, see Page targeting.

Flow frequency limit

If your account uses the Experiences frequency limit, this Flow counts toward it by default. Toggle the override in the Flow settings to exempt this Flow from the limit — useful when the Flow is critical to the Workflow sequence and must be seen regardless of how many other experiences the user has encountered recently.

Audience

The Flow inherits audience targeting from the Workflow's Start node. You don't set a separate audience on the Flow itself.

If the Flow isn't appearing

• Confirm the user is logged into your app and on a page that matches the URL targeting conditions.
• Check that the user has reached the Flow node in the Workflow — open the user's profile in Studio and review their Workflow progress.
• If frequency is set to "Show Once," the user may have already seen it. Reset their Flow history from their profile page to test again.
• Verify the Experiences frequency limit isn't blocking it. If it is, enable the override on this Flow node.
• Open the Appcues debugger and confirm all rows show green checkmarks.