📦 Published Templates Can Now Be Updated
Publishing an automation to the template store is no longer the last step.
Until now, once you published a template, it stayed as it was. If you found a bug, wanted to add a step, or needed to improve the description, there was nothing you could do except publish again. Now you can update a template you’ve published, and the changes carry over to the published version.
What’s new
Edit after publishing. Fix the flow, add a step, or clarify the description. The published template follows your changes.
No more starting over. People who use your template don’t have to import it from scratch every time you improve it.
You share the working version. If a deployed version of your automation exists, the template is based on that version. What you share is your working copy, not a draft you left in trial.
Why it matters
Templates are rarely perfect on the first try. Apps change, edge cases show up, and users ask for clearer instructions. Being able to update a template lets you keep it accurate and useful over time, without creating duplicates or asking people to look for a new version.
Good to know
Because the template is based on your deployed version, deploy your automation first if you want the latest changes to be what people get.
You can still share a template with a private link instead of listing it publicly.
Learn more
📘 Automation Templates: how to publish a template and share it with a private link