Also known as: trigger Appcues content, chain flows, linked flows, flow sequence.

How linking works

When a user completes Flow A, Appcues automatically launches Flow B. Linking uses the Trigger Appcues content completion action on the Flow settings page.

Key behaviors:

• Linking overrides all targeting on the triggered Flow. Flow B shows to anyone who completes Flow A, regardless of Flow B's audience, page targeting, or frequency settings.
• All linked Flows must be published. If Flow B is in draft, it won't appear after Flow A completes.
• If the triggered Flow is on a different page, combine "Trigger Appcues content" with "Redirect to a different page" so the user arrives at the correct URL first.

Link two Flows

1. Open the Flow you want to show first (Flow A) and go to the settings page.
2. Scroll to Flow Completion Actions at the bottom.
3. Select Trigger Appcues content and choose the Flow you want to trigger (Flow B) from the dropdown.
4. If Flow B is on a different page, also select Redirect to a different page and enter the destination URL.
5. Click Publish (or Push Changes if already live).

Repeat to chain more Flows — Flow B can trigger Flow C, and so on.

Set triggered Flows to "Show manually"

If a linked Flow should only appear when triggered by another Flow (not independently), set its trigger to Only manually. This prevents it from showing on its own when a user reaches the page.

Test linked Flows

You can't preview a full linked sequence in the Builder — the Builder only shows one Flow at a time.

To test:

1. Publish all Flows in the chain.
2. Restrict the audience to your own User ID (add an audience condition: User ID is [your ID]).
3. Walk through Flow A on the live site. When you complete it, Flow B should appear automatically.
4. After testing, remove the User ID restriction and republish.

Troubleshoot linked Flows

Flow B doesn't appear after completing Flow A. Check that Flow B is published. Unpublished Flows can't be triggered. Also confirm the completion action is set to "Trigger Appcues content" with the correct Flow selected.

Flow B appears on the wrong page. If Flow B targets a different URL, add "Redirect to a different page" alongside "Trigger Appcues content." For a different domain, enter the full URL including https://.

Flow B shows independently when users visit the page. Flow B's trigger is probably set to "When the user reaches the page." Change it to Only manually so it only fires when triggered by Flow A.

Priority weight is overriding the chain. If you've set a priority weight on the triggered Flow, it can interfere with the trigger chain. Remove any manually set weights on linked Flows. See Set Flow priorities.