Branching Logic with Paths
Sveip for å vise menyen
Paths let a single Zap branch into multiple workflows based on conditions. Unlike filters, which make pass/fail decisions, paths route data into different tracks, each with its own actions. One trigger, multiple outcomes.
Filters answer Should this Zap continue. Paths answer Which route should it take. With paths, data is routed into different branches like A, B, or C, each with its own actions. Same trigger, different paths.
Path Structure
When you add a Paths step, you create a branching point. From there, your Zap splits into multiple parallel tracks.
Conditions are rules that determine whether a particular path in your Zap should run.
-
Work exactly like filter conditions;
-
Check fields against values, such as equals, contains, or greater than.
Actions are the steps that execute if the conditions for a path are met.
-
Each path has its own independent set of actions;
-
Paths can have completely different workflows.
# Trigger
↓
# [Previous Steps]
↓
# ┌─────────────────────────────────────────────────────────┐
# │ PATHS │
# ├─────────────────┬─────────────────┬─────────────────────┤
# │ Path A │ Path B │ Path C │
# │ (Conditions) │ (Conditions) │ (Conditions) │
# │ ↓ │ ↓ │ ↓ │
# │ Action 1 │ Action 1 │ Action 1 │
# │ Action 2 │ Action 2 │ Action 2 │
# │ Action 3 │ │ Action 3 │
# │ │ │ Action 4 │
# └─────────────────┴─────────────────┴─────────────────────┘
Each path runs independently with its own actions. If data matches more than one path, Zapier evaluates all paths and runs every qualifying one, it does not stop at the first match.
As a result, overlapping conditions can trigger multiple workflows at once. A single record can match Path A, B, and C simultaneously, causing all their actions to run.
Paths are not mutually exclusive. If you need only one route to run, design conditions that do not overlap.
Takk for tilbakemeldingene dine!
Spør AI
Spør AI
Spør om hva du vil, eller prøv ett av de foreslåtte spørsmålene for å starte chatten vår
