Operations, Workflows, Automations, Discover tab. Two ways to avoid a blank canvas: a library of ready-made workflows, and an AI copilot that drafts one from a description.
The Template Library
Templates are tiered by complexity, and the tiers are honest:
| Tier | What it involves |
|---|---|
| Starter | Single trigger, single action |
| Intermediate | Conditions and branches |
| Advanced | Loops, switches, transforms |
| Expert | Cross-area orchestration with AI |
Templates are grouped by the area they serve, so you can find the ones relevant to your department.
Use Templates To Learn, Not Just To Ship
The most valuable thing about a template is not that it saves you building. It is that it shows you a working shape.
Open an Intermediate template even if you only need a Starter. Look at where the condition sits, how the branches are attached, what the end nodes do. Ten minutes reading two templates teaches the builder better than any documentation.
Tip
Start at Starter even when your eventual workflow is complex. One trigger and one action, activated and verified running, is worth more than an elaborate flow you are not sure fires. Add the second step after the first has run in production.
Adapting A Template
- Open it and read every node before changing anything.
- Change the specifics - which pipeline, which recipient, which template.
- Check the prerequisites of every action. A template using WhatsApp assumes you have an approved template.
- Dry run.
- Save and activate.
- Check the first live execution in Automation Health.
The step people skip is the third. A template is a shape, not a working configuration - it cannot know whether your channel is connected.
The AI Copilot
Describe what you want in plain language and a workflow is drafted: nodes laid out, trigger chosen, actions configured.
It is good at the shape. It is a starting point, not an answer.
Always do this before activating a drafted workflow:
- Open every node. Check the trigger is the event you actually want - a draft often picks a broad event where a specific one exists.
- Check every action's configuration, especially recipients and templates.
- Check the branches go where you expect. A drafted condition may test the right field the wrong way round.
- Dry run and confirm both paths.
Caution
A drafted workflow is confident-looking and can be subtly wrong in ways that are expensive - a condition inverted so the wrong branch sends, a trigger too broad so it fires on every edit. Review it exactly as you would review a colleague's first draft: assume it is roughly right and specifically wrong.
Writing A Good Description
The copilot works from what you tell it, so:
- Name the moment. "When a deal is marked won" beats "for won deals".
- Name the recipient. "Email the deal owner" beats "send a notification".
- Name the condition. "Only if the value is over 10,000."
- Keep it to one job. A description containing "and then also" produces a workflow doing two things badly. Build two.
Templates Versus Copilot
Template when something close to what you want exists. It is verified and you can read it.
Copilot when nothing fits, or when you want a starting layout for something unusual.
Either way the work is the same: review, dry run, activate, verify the first live run.
Common Questions
Can I save my own workflow as a template? The library is system-provided. Duplicate an existing workflow of your own as a starting point for a similar one.
The copilot used an action I have not set up. That is the prerequisite check. Set the channel up, or swap the action for one you can support.
Can I ask it to change an existing workflow? Treat drafting as a starting point for new workflows. Editing existing ones is safer done by hand, where you can see exactly what changed.
Did this answer your question?
No, ask a person