Path (Zapier)

A path adds branching logic to a Zap. Instead of running the same actions every time, a path routes each run down a different branch depending on which conditions match. It lets one trigger handle several outcomes — record found vs. not found, large payment vs. small — inside a single workflow.

How paths work

Each path branch has its own rules, defined with the same and/or logic as a filter. A branch can be set to:

• Custom rules — run only when its conditions are met.
• Always run — run every time regardless of data.
• Fallback — run when no other branch qualified.

Branches evaluate in order, and each branch contains its own actions. You can add up to 10 branches in a path group and nest path groups a few levels deep for more complex trees.

Paths vs filters

A filter is a single yes/no gate. A path is a fork: it doesn't just stop or continue, it chooses which set of actions to run. Reach for a path when the same event should trigger genuinely different responses.

Task usage

Paths themselves don't consume a task — only the actions inside a branch that actually runs do. A run that takes the "large payment" branch bills for that branch's actions and nothing else.

Why it matters

Paths keep related logic in one place. Rather than building three near-identical Zaps for three payment sizes, a single Zap with three branches routes each event to the right notification or record — clearer to maintain and cheaper than duplicating whole workflows.