Visual workflow automation with real branching logic.
Scenarios are the heart of Make. Each module is a typed operation with explicit input and output mapping, which is what makes multi-branch business logic practical to build and — more importantly — practical to maintain six months later.
Disclosure: We may earn a commission if you purchase through links on this page. This never affects our reviews.
Split a flow into conditional paths with per-path filters.
Walk arrays item-by-item, then recombine the results into one bundle.
Persist state between runs without bolting on an external database.
Retry, break, resume or route failures instead of silently halting.
Trigger scenarios the moment an event fires, not on a polling interval.
Inspect every bundle in every module for any past run.
The canonical Make pattern: search first, branch on result, then create or update.
Operations are billed per module execution — most scenarios waste them.
Roughly one per module execution. A six-module scenario running 1,000 times uses about 6,000 operations.
Yes — the generic HTTP module handles any documented REST API when no native connector exists.
