Automation templates
An automation's entire workflow, the trigger, conditions, actions, and field mappings, can be saved as a template and reused when creating new automations. Templates capture the logic once so the same structure doesn't need rebuilding from scratch each time a similar workflow is needed.
Saving an automation as a template
Any active or draft automation can be saved as a template from the automation editor. The template preserves the node layout, trigger type, condition logic, action configuration, and field mappings. Once saved, the template appears in the template library for selection when building new automations.
Creating an automation from a template
When creating a new automation, selecting a template from the library pre-populates the canvas with the saved nodes and configuration. The trigger's entity filter (which form, which project, which status) can be adjusted to match the new context, and action fields can be remapped to different entities. The template provides the structure, and the adjustments tailor the automation to its specific purpose.
Community automation recipes
The template library includes community-shared automation recipes covering common workflows like client onboarding, invoice follow-ups, task assignment, and booking confirmations. Installing a community template creates a local copy, so any node can be modified, removed, or extended without affecting the original recipe.
Standardising workflows with templates
Templates make it possible to standardise how events are handled across your workspace. A "new client onboarding" template applied consistently ensures every new client triggers the same project setup, welcome email, and task assignment, so the process stays uniform regardless of who initiates the workflow.
