Paths in workflows

Feature Requests
1

Feature request for paths in workflows. Right now I get around paths by either using Zapier (or someone could use Make), or by having two or more workflows, each for the particular “path” that I want, with a filter step for each that governs when each workflow should run.

Ideally, users could build one single workflow that could end in many different results (i.e. paths) directly within Noloco rather than relying on a 3P tool, especially as Noloco’s workflows are native to the platform and therefore quite fast.

5 Likes
2

100% Agreed. I always have this issue and hate taking it out of Noloco! Thanks for the suggestion Joel!

2 Likes
3

Bumping this up again as this is me and my clients’ top need regarding automations. The workaround is that you have multiple automations with filter steps, each firing when appropriate, but it is cumbersome, has more development ramifications, and pushes us toward 3P tools like Make or Zapier to supplement our Noloco workflows.

1 Like