Paths#

What are Paths?#

Paths let you build advanced workflows to run different actions based on conditions you decide. Paths are Zapier's conditional logic tool. Think of Paths as If/then logic: if A happens in your trigger app, then do this, if B happens then do something else, and so on.

How to Get Started with Paths on Zapier#

See our Getting Started with Paths guide with instructions for how to set up Paths with your own Zaps. Please note: Paths are available on Professional plans and higher.

You can try Paths free for 7 days if you're on a Free or Starter plan. To activate your trial, add a Paths step to any Zap and accept the offer.

Terminology#

Path Group#

A path group is a group of Paths on the same level. Adding a Paths step will automatically create two Paths in a single Path Group. From there, you can add or delete Paths to fit your needs.

Path Group

Path Rules#

Similar to how Filters work, each Path has a rule or condition that determines whether or not the triggering activity will performs the steps in that Path.

Path Rules

It's possible for more than one Path's rules to be met resulting in more than one Path running in a single Zap.

Common Questions#

What accounts have access to Paths?#

Paths are available for accounts on the Professional, Professional Plus, and Teams plans.

If you’re on a Free or Starter plan, you can try Paths for free for 7 days. Just add a Paths step to a Zap and you can start your free trial from the editor.

Once your trial expires, you’ll need to upgrade to a Professional plan to keep using Paths. If you don’t upgrade, you’ll automatically lose access to Paths and we’ll pause any Zaps using this feature.

How many Paths can be placed in a Path Group?#

A single Path Group can have up to three Paths in it. Please reach out to our support team to let us know if your needs require more Paths. We want to know about it!

How many Tasks are used with Paths?#

Tasks are counted similar to how they are counted for Zaps with a Filter step.

When a Path's rules are met, this counts as one Task. Then, every step in the Path that runs successfully counts as another Task.

For a Path Group, if none of the Path's rules are met, then no Tasks are used.

How many Paths will run?#

If the conditions for a Path's rules are met, that Path will run. It's possible for all or none of the Paths to run.

Can I build a Path within a Path?#

Yes! These are called nested Paths.

A single Zap can have up to three Paths per Path Group and nested Paths up to three levels deep. Please reach out to our support team to let us know if your needs require more Paths. We want to know about it!

Why can't I add steps after my Path Group?#

Paths may only be added as the last step in a Zap. If you need the same steps performed at the end of a Zap, these will need to be added within each Path.

Please reach out to our support team to let us know what type of workflow you want to use with Paths that would require steps to run after a Path step. We want to know about it!

How do I use if/else logic with Paths?#

Each Path's rules do not interact with the rules for another Path. This means it's possible for all Paths in a single Path Group to run, for none of the Paths to run, or any number in between.

Thus, there is no "else" logic built into Paths. To implement if/else logic, set the rules for your Paths to implement an "inverse" condition, for example:

  • Path A - email exists
  • Path B - email does not exist
↑ Was this documentation useful? Yes No (Suggest Edits)
Get Help