Organizing Action Flows with folders

As your library of Action Flows grows, keeping them organized becomes important - both for your own productivity and for making it easier for your team to find and manage Action Flows. Atomic's folder system lets you group related Action Flows together, with support for up to three levels of nesting so you can reflect the structure that makes most sense for your team.

The folder panel on the Action Flow dashboard showing a nested folder tree

Why use folders?

Folders are optional, but they become very useful once you have more than a handful of Action Flows. Here are some common ways teams use them:

• By product area or feature - Group Action Flows for onboarding, billing, and support separately so each team can quickly find what they own.
• By campaign or initiative - Keep Action Flows related to a specific campaign together for easy review before and after launch.
• By status or workflow stage - For example, a Templates folder for draft Action Flows your team clones from, and separate folders for Action Flows that are live in production.
• By region or audience - If you operate in multiple markets, separate folders make it easy to see what's running where.
• By trigger type - For teams managing many Action Flows, grouping by trigger type (scheduled, event-driven, batch) helps with at-a-glance understanding.

tip

Consider creating a Templates folder and populating it with well-designed Action Flows your team can clone as a starting point. This is a great way to promote consistency and save time.

The folder panel

The folder panel appears on the left side of the Action Flow dashboard. It shows:

• Uncategorized - Action Flows that haven't been assigned to a folder yet. This always appears at the top.
• Your folders - Listed as a tree. Folders with sub-folders show a chevron (▶) you can click to expand or collapse them.
• A search box to filter the folder list by name. When searching, the full path of nested folders is shown (e.g. Onboarding > Welcome series) so you can tell folders apart even if they share a name.

Clicking a folder in the panel filters the main list to show only the Action Flows inside that folder.

Searching folders shows the full path for nested folders, and highlights the matched text

Browse folders

Beta feature

Browse folders is in beta and may be subject to change. Please contact us to provide feedback.

For organizations with deep folder structures, the Browse folders view offers a quicker way to navigate. It shows your folders in side-by-side columns, with the Action Flows inside each selected folder listed inline alongside its sub-folders, so you can drill down without losing sight of where you started.

To open it, click the Browse folders icon (a folder with a magnifying glass) next to the search bar at the top of the Action Flows list. The icon only appears once your organization has at least one folder.

Browse folders shows your folders side-by-side in columns, with the Action Flows inside each selected folder listed inline

To use it:

1. Click a folder in the leftmost column. A new column appears to the right showing its sub-folders, and any Action Flows inside that folder are listed inline below them.
2. Keep clicking through to drill deeper, up to the maximum nesting depth.
3. Click an Action Flow row to navigate straight to it.
4. Use the back-arrow on a column header, or click any folder in a previous column, to step back up the tree.

Moving Action Flows between folders by drag and drop

Inside the Browse folders view you can move an Action Flow into a different folder by dragging it.

1. Open Browse folders and drill into the folder containing the flow you want to move.
2. Drag the Action Flow row.
3. Drop it onto any folder in any column to move it there. Drop it onto Uncategorized in the leftmost column to remove it from all folders.

The flow moves immediately. Any open folder views refresh so the flow disappears from its old folder and appears in its new one without a manual reload.

info

Drag and drop is only available inside the Browse folders view. The main Action Flows list does not support drag and drop - to move a flow from there, use Add to folder from the ⋯ overflow menu instead.

Creating a folder

1. In the folder panel, click the + button next to the Folders heading.
2. Enter a name for your folder. Folder names can contain letters, numbers, spaces, hyphens, and underscores.
3. Click Create.

Your new folder will appear in the panel and you can start moving Action Flows into it straight away.

Creating a sub-folder

Folders support up to three levels of nesting — a top-level folder, a sub-folder inside it, and one further level beneath that.

To create a sub-folder:

1. In the folder panel, hover over the folder you want to nest inside.
2. Click the + icon that appears on the right side of the folder row.
3. In the Create a new sub-folder dialog, enter a name for the sub-folder.
4. Click Create.

The parent folder will automatically expand to show the new sub-folder once it's created.

info

The + button only appears on folders that can still accept sub-folders. If a folder is already at the maximum nesting depth, the button won't be shown.

Adding an Action Flow into a folder

You can assign any Action Flow to a folder at any time, regardless of whether it's published or still in draft.

1. From the Action Flow list, find the flow you want to move.
2. Click the ⋯ overflow menu on the right side of its row.
3. Select Add to folder.
4. At the top of the dialog, choose how you want to find the destination folder:
   • Dropdown - the original list view. Pick a folder from the dropdown; nested folders are shown with their full path (e.g. Campaigns > Q3 > Email follow-up) so you can easily tell them apart.
   • Browser - the same side-by-side column layout used by Browse folders, except Action Flows are hidden so the focus stays on choosing the destination folder. Useful for picking from a deep folder structure.
5. Select the destination folder, then click Save.

tip

You can also create a new folder directly from the Add to folder dialog - in the Dropdown view, click + New folder at the bottom of the list and optionally choose a parent folder to nest it under.

Renaming a folder

1. In the folder panel, click the folder you want to rename to select it.
2. In the panel header area that appears, click Edit folder.
3. Update the name and press Enter or click Save changes.

Deleting a folder

1. In the folder panel, click the folder you want to delete to select it.
2. Click the ⋯ overflow menu in the folder header area.
3. Select Delete folder and confirm.

warning

A folder cannot be deleted if it contains sub-folders. Deleting a folder does not delete the Action Flows inside it - they will be moved to Uncategorized.

Folders in analytics

When an Action Flow is triggered, the ID of the folder it belongs to is captured as workbenchFolderIds in the platformContext of every analytics event that flow generates. This lets you filter or segment analytics data by folder in downstream tools.

See Analytics event reference for the full list of platformContext properties.

You can also filter the Insights dashboard by one or more folders, scoping all metrics to Action Flows within those folders.

Sorting folders

You can change the order in which folders appear in the panel. Click the ⋯ overflow menu next to the Folders heading and choose from:

• Recently edited - Folders whose contents were most recently updated appear first.
• Ascending (A–Z) - Alphabetical order.
• Descending (Z–A) - Reverse alphabetical order.

Your chosen sort order is remembered between sessions.

Restricting access to specific folders

Preview feature

Folder-scoped access is in preview and may be subject to change. Please contact us to provide feedback.

Workbench administrators can limit a permission group's Action Flow access to one or more top-level folders. Members of a restricted group can only see and edit Action Flows filed within those folders (and their sub-folders). This is useful when separate teams manage distinct product areas and should not have visibility into each other's Action Flows.

See Workbench permissions - Action Flow folder access for how to configure this.