Help · Automation and workflows
The workflow templates gallery
Prebuilt automations you install as a draft in one click, then adapt. Faster than a blank flow, and a good way to see how the pieces fit together.
Updated August 2026
The hardest part of a first automation is not building it, it is knowing what to build. Templates solve that by showing finished examples you can read and adapt.
They install as drafts, so nothing starts running because you were curious.
Who this is for
Anyone new to automation, and experienced users who would rather start from a recipe.
Before you start
- Permission to create workflows.
- Whatever the template depends on — a pipeline, a template, an integration — depending on which one you pick.
Installed as a draft, not switched on
Installing a template does not start it running. It arrives as a draft for you to read, adapt and then activate deliberately. That makes the gallery safe to browse and install from while you are still learning what the pieces do.
Use a template
- Browse for something close to your problem
It does not have to be exact. A template that is roughly right is a better starting point than a blank flow. - Install it as a draft
One click. Nothing runs yet — you now have a complete flow to read. - Read it before changing it
Templates are the clearest available documentation of how triggers, conditions and actions fit together. Reading one teaches more than the concepts do. - Adapt it to your setup
Change the trigger, tighten the condition, point the actions at your own templates and people. The structure survives; the specifics are yours. - Dry-run it
Adapted or not, dry-run before activating. A template built for a different setup can match far more than you expect in yours. - Turn it on
Activate deliberately once the dry run matches expectation.
What you get
- A working automation faster than building from scratch.
- A readable example of how the pieces fit together.
- Safe browsing, because installs arrive as drafts.
- A structure to adapt rather than a blank canvas.
Frequently asked questions
Does installing a template turn it on?
No. It installs as a draft. You adapt it and activate it deliberately, which is what makes the gallery safe to explore.
Should I use a template or build from scratch?
Start from a template if anything is close. Even one you end up changing heavily teaches you the shape faster than a blank flow.
Do I still need to dry-run an installed template?
Yes. It was written for a generic setup, not yours — its conditions may match very differently against your data.
Can I make my own templates?
The gallery ships with prebuilt ones. For your own repeated patterns, duplicating an existing workflow is the practical equivalent.
Related articles
Build your first workflow
Pick a trigger, add a condition, drop in an action, dry-run it, and turn on a live, no-code workflow — the full path from a blank flow to automation that runs on its own.
Read articleDry-run a workflow before turning it on
See what a workflow would do without it doing anything. The dry run is the cheapest way to find out that your condition matches four thousand records instead of four.
Read articleHave an account issue this guide doesn't cover?
Start free today
Ready to give your team a CRM they'll actually use?
Start free. Bring your whole team. Cancel whenever (you won't).