Start from a template
A template is a complete workflow: trigger, steps and sensible defaults. You create a copy, fill in the few things only you can know, test it and turn it on. There are more than 140 templates.
Create a workflow from a template
- Open Workflows and select Browse templates. On a store without workflows, the template gallery is offered on the empty page.
- In Start from a template, use Search templates or the Category filter.
- Each card shows what the template does, how many steps it has and, under After creating, what you still need to set up.
- Select Use template. The editor opens with the new workflow. It is turned off.
- Work through the setup notes. A banner at the top of the editor repeats them.
- Select Test, check the result, then Save and Turn on.
The categories
| Category | Examples |
|---|---|
| Orders | Tag high-value orders, post new orders to Slack, cancel orders that stay unpaid |
| Risk and fraud | Tag or hold high-risk orders, alert the team about chargebacks |
| Fulfillment and returns | Alert when an order is not fulfilled in time, ask for a review after delivery |
| Products | Mark new products as new for 30 days, keep products without images as drafts |
| Inventory | Low stock alert, hide products that are sold out, bring them back when stock returns |
| Customers | Welcome email, sort customers into bronze, silver and gold, win back customers |
| B2B and draft orders | Announce new companies, send the invoice when a draft order gets a tag |
| Discounts and checkouts | Remind customers about an abandoned checkout, delete discount codes when they expire |
| Storefront behaviour | Spot searches that find nothing, measure demand for sold-out variants |
| Custom data | Turn a product metafield into a tag, watch one field of a metaobject |
| Reports and schedules | Daily sales summary by email, weekly list of orders waiting for payment |
| Data sync | Send paid orders to another system, let another system set stock by SKU |
| Files and SFTP | Set stock from a daily CSV file on your SFTP server, email a daily file |
| Maintenance | Archive completed orders every night, delete old draft orders every week |
What the setup notes usually ask for
- A secret. Templates never ask you to paste a key or a webhook URL into a step. They read a secret such as
{{ secrets.SLACK_WEBHOOK_URL }}, and the note tells you which name to create on the Secrets page. See Secrets. - A threshold or a tag. For example the order total that counts as high value.
- A sender. Templates that send email need a sender under Email senders. See Send email and email senders.
- A time. Scheduled templates ask you to set the time and your time zone on the trigger.
- A permission. If the workflow needs store data that is not granted yet, the editor shows This workflow needs permissions with a button to the Permissions page.
A template is a starting point
The new workflow is yours. Change the trigger filter, add steps, remove what you do not need. The template itself is not linked to it, so later changes to a template do not change your workflow.
The Recipes section of these docs walks through some templates step by step, for example Recipe: tag high-value orders and Recipe: low stock alert to Slack.