Starting from a Workflow Template
The template gallery provides pre-built starting points for common automations. Instead of building from a blank canvas, pick a template that matches your use case and customise it to your account.
Opening the Gallery
- Navigate to Workflows.
- Click Browse Templates.
- Filter by category or search by name.
- Click a template card to see the full description, trigger, and action tree.
- Click Use Template to instantiate it.
Available Templates
The gallery includes templates across many categories:
- Helpdesk: Classify Inbound Ticket, Auto-Acknowledge Inbound Email, Satisfaction Survey Follow-Up, Weekly Stale Tickets Digest.
- DevOps: New Issue to Sprint, Sprint Start Welcome, Test Execution Failure Issue.
- Tasks: Overdue Task Reminder.
- Compliance: Policy Published Acknowledgement, Data Breach 72-Hour Reminder.
- Incidents: Escalate Critical Incident.
- Sales: Lead Welcome Flow, Deal Won Celebration.
- General: Summarize and Email, New Note Slack Mirror.
What Gets Copied
Template instantiation preserves the full definition:
- Every action in the tree, including nested for-each and branch children.
- Schedule configuration for scheduled templates.
- Trigger event configuration (field filters, offsets, thresholds, and so on).
- Shared mailbox bindings for email-sending workflows.
- Rate limit and alerting thresholds.
- Custom object bindings for Entry triggers.
This is a change from earlier releases, where templates sometimes produced an incomplete shell with schedules and nested children silently discarded. Every template now instantiates fully.
Disabled by Default
New workflows from templates are created in the disabled state. Review the trigger, conditions, and actions, fill in any account-specific values (recipient addresses, mailbox selections, channel IDs), then flip the Enabled toggle to activate.
Bindings
Some templates declare bindings, which are placeholders the template author expects you to fill in at instantiation time (for example, the email address to send the digest to, or the user group to notify). The instantiation dialog prompts for each binding, validates it, and substitutes the value into the resulting workflow.
Customising Further
After instantiation, the workflow is a regular workflow. Edit any action, add new steps, rewire branches, or change the schedule. The template is just a starting point. You can even export your customised workflow as JSON and share it with another account through import.
Feature Flags
Templates that depend on gated features (AI actions, webhooks, subworkflows, and so on) are hidden from the gallery unless the matching feature flag is enabled on your account. This prevents you from instantiating a template that cannot run.