Zapier, n8n or Make.
The recipe is the product, and a recipe is not tied to one kitchen. Every template ships for all three: a Zapier build guide, an importable n8n workflow, and a Make build guide.
One purchase, three formats.
Zapier
The blueprint and setup guide: trigger, action events, and the full field mapping including the copy and timing. Where a guided template has been built, the guide also carries a link that installs the whole thing with the values already filled in.
n8n
A workflow JSON you import. The steps arrive on the canvas wired in order and mostly already configured — 342 of 479 nodes come with their fields filled in, not blank. Whatever an import cannot carry stays in a sticky note under the node. All 77 of our 77 templates ship this way.
Make
A Make-specific build guide: every module in order, every field value, plus the concept translations that catch people out coming from Zapier — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.
97% of steps land on a native node.
Across 77 workflows and 479 steps, 465 map to a real n8n node. 66 of the workflows are native end to end. The rest arrive as an HTTP Request node with the reason written into the sticky note beside it.
That is deliberate. An empty HTTP Request node is visibly unfinished and you will go and finish it. A plausible-looking wrong node is not, and nobody checks a node that looks configured.
Why isn’t the Make version an import?
Because we would have to guess. A Make blueprint identifies every module by an internal string that Make does not publish, and a blueprint containing a wrong one imports as a broken scenario. Generating 77 files from guessed identifiers would mean shipping 77 files that mostly do not work.
The same rule decides what goes into an n8n node and what does not. A parameter is written in only when it was checked against the schema a real n8n publishes for that node; anything that would have to be guessed is left blank and named in the sticky note instead. A workflow that imports cleanly and then quietly does the wrong thing is the worst outcome of the three, so we do not build toward it.
See a real one
Browse the library and open any template — each page lists exactly what it ships for.