Paths let you create conditional branches inside a flow. Each path runs different actions based on one or more rules you define, so a single flow can handle multiple outcomes. You can build variations into one flow instead of having several similar flows. Use paths to:

• Send files to different folders based on project name
• Notify specific teams depending on a proof’s status
• Start different integrations depending on file type or metadata

Available on: Pro Enterprise

Paths  are decision points in your flow. When a flow reaches a path, it evaluates the conditions you set:

• If the conditions for path A are met, it runs the actions assigned to path A.
• If they aren’t, it checks the next path, and so on.
• Multiple paths can exist in the same flow.
• Rules can use built-in tokens such as proof name, version number, status, tags, or custom metadata.

Tip: Set a default path that runs if none of the other conditions are met.

To add a path to a flow:

1. In the Connect tab, select Create a new flow, select and configure an event trigger, and select Next.
2. Under Choose a Zibot, select create a path.
3. Enter a path name. By default it is "Path A", "Path B", and so on.
4. Configure rules for the path:
   Select conditions from the available tokens and operators.
   You can add multiple rules to one path.
   Combine rules with AND/OR logic as needed.
   
   
   
    
5. Select Next. The Flow pane creates a + within the path. 
   
   
6. Select the + to add actions to your conditional path. When a path’s conditions are met, your flow executes the actions you’ve added after it.
7. Select the + outside the path to add another path if desired, and additional actions.
8. Review the diagram in the Flow pane to confirm the path structure.
   
   
9. In the Summary, select Save and Turn on.

Tips for using paths effectively

• Group related rules in the same path to keep flows manageable.
• Use tokens wherever possible so the path adapts to different proofs or projects.
• Always include a default path to handle unexpected data.
• Keep path names descriptive so your team can understand them at a glance.