Step Templates
Fork a Step template to clone a complete, editable automation canvas into your own workspace. You can customize its triggers, Steps, connections, and routing logic without affecting the original template.
- Use it to
- Clone a full, editable automation canvas from the Marketplace so builders can customize triggers, Steps, and branches
- Find it
- Left sidebar → Marketplace → Use template (or Deployment → Interface: Step)
- Cost
- Free to fork · Normal Step credit and Glow AI token rates when running your copy
- Limits
- Source credentials, remote pickers, and email defaults are stripped on copy · Steps renumber 1..N automatically
- Output
- An independent, editable Draft automation canvas in your active workspace
- Instead
- Form Templates (/getting-started/templates/form-templates) when end-users should supply inputs through a form without editing the canvas
Choosing the Right Template Type
The interface type decides how someone uses the automation; publishing makes a version available to others. Configuring a form does not publish it.
- Clones the full editable canvas into the recipient workspace.
- Recipients can add, remove, or rewire triggers, Steps, and logic.
- Best when the recipient will customize and maintain the automation.
- Presents selected Step fields as a guided input form.
- Runners supply inputs and click Run without editing the canvas.
- Does not alter workspace role or automation access permissions.
See Building a Form Interface for field configuration, or Finding a Template to browse the Marketplace.
Forking a Template
Follow Forking a Template to acquire a copy. Changes to its Steps and configuration do not change the original template, and source updates are not automatically applied to your copy.
Before running a fork: Review each Step’s configuration and select or connect the intended accounts in your workspace. Check data mappings and use test destinations. Running the copy can send messages or change records in the connected apps.
Publishing your automations as templates
Follow Publishing an Automation as a Template for version selection and field-sanitization checks before publishing. Forked automations cannot be republished; build in a new automation if you want to share an adapted version.
Best practices for builders
Use the template preparation checklist to document prerequisites, explain the Steps, and test each route before sharing.
- Run
- Open a Step template in the Marketplace, click Use template, and confirm your target workspace and visibility
- You should see
- Glow creates an editable Draft copy of the full canvas numbered 1..N in your selected workspace.
What’s Next?
- Give non-technical users a form instead of the canvas with Form Templates.
- Publishing Templates: publish and update a version for others to use.