Reuse One Menu Across a Multi-Screen Flow
Define a menu once with the New Navigation Item Collection action, show it on every screen, and route the agent to the screen they pick with a Decision.
Some flows outgrow one screen. A service agent working an account moves between an overview, a contacts screen, an opportunities screen and a cases screen, each with its own components and its own validation. A side menu on every screen lets the agent jump to any of them in one click, in any order. You define the menu once, and a Decision sends the agent where they clicked.

Before you start
A screen flow that receives the account Id, for example a text input variable
recordId.The New Navigation Item Collection action page, for the fields each item accepts, and the Navigation reference for the component settings.
If the four views fit on one screen, tabs on one screen are simpler. Use this pattern when each view needs its own screen.
How the flow is shaped
The flow runs in a loop: build the menu once, then a Decision picks the screen, the agent clicks a menu item, an Assignment stores the item, and the flow goes back to the Decision. In the figure, a Get Records on the account also runs before the Decision, for the fields the screens display.

Steps
Build the menu once with the action
At the start of the flow, add an Action element and pick New Navigation Item Collection (category Avonni). Name it
Build_Menu.Under Navigation Items, add four items with these Label and Value pairs: Overview
overview, Contactscontacts, Opportunitiesopportunities, Casescases.
Flow Builder stores the action's output, a collection of navigation items, under the action's name. Every screen will read the same Build_Menu output, so a new item added here appears on all screens at once.
Add the router Decision
Add a Decision element after the action, named Route. Create one outcome per item, in menu order:
Outcome Overview:
{!activeItem}EqualsoverviewOutcome Contacts:
{!activeItem}Equalscontactsand so on for
opportunitiesandcases.
Point the default outcome to the Overview screen too, so an unexpected value never strands the agent.
Add the Navigation to each screen
On each outcome, add a Screen element with an Avonni Navigation on it, then your own components for that view. In the Component Builder of each Navigation:
Set Orientation to Vertical for a side menu.
Choose the Variable data source. Under Items Collection, choose Custom and type
Build_Menu, the action's API name (the dropdown does not list action outputs).Set Active Navigation Item Value to
{!activeItem}, so the menu highlights the screen the agent is on.
Leave the screen when an item is clicked
On each Navigation, open the Interactions tab and add a Select interaction:
Leave Target Name empty. An empty target fires for every item, which is what a menu needs.
Set Type to Flow Navigation. A second Type field appears: set it to Next Screen.
The Navigation sets Active Navigation Item Value to the clicked item before it moves the flow on, so the value is ready on the next element. See Flow Navigation for the other navigation types.

Store the clicked item and loop back
After each screen, add an Assignment: {!activeItem} Equals that screen's Navigation > Active Navigation Item Value (for example {!ContactsMenu.activeNavigationItemValue}). Connect the Assignment back to the Route Decision.
Each screen needs its own Assignment, because each Navigation has its own API name. Connect back to the Decision, not to the action: the menu is already built.
Troubleshooting
Related tutorials
Build tabs on one screen with Navigation: the same menu without leaving the screen.
Building a navigation menu with related records: a menu whose items are the account's records.
Creating navigational screen flows in router mode: the same router idea with a clickable Progress Indicator.
Was this helpful?
