Publishing Templates
Publish a saved automation version to the public Marketplace or deploy independent copies to managed client workspaces. Choose Workflow Settings for Marketplace-only listings or the deployment modal for client delivery.
- Use it to
- Publish a saved automation version to the public Marketplace or deploy independent Draft copies to up to 50 managed client workspaces
- Find it
- Canvas → Share → Deploy, Canvas → Workflow Settings, or Left sidebar → Deployment
- Cost
- Free to publish and deploy · Glow covers AI usage for Generate descriptions
- Limits
- Only automations created from a blank canvas can be published · Submissions are validated and reviewed by Glow before listing
- Output
- A versioned Marketplace template listing or independent Draft copies in target client workspaces
- Instead
- Automation Visibility and Sharing (/build/core-concepts/workflow-visibility) when sharing a single live canvas with teammates in the same workspace
An automation you created from a blank canvas can be published by its owner, a workspace Admin, or a Manager. An automation forked from another template cannot be republished; start a new automation if you intend to share an adapted version.
Publishing an automation as a template
Choose the entry point for your destination. Both routes publish a selected version to the same Marketplace, but only the deployment modal also offers client destinations in an MSP workspace.
| Destination | Entry point | Procedure |
|---|---|---|
| Marketplace, managed clients, or both | Share → Deploy on the canvas, or Deploy on the Deployment page | The Versioned Deployment Flow. |
| Edit listing or publish a version | Workflow Settings on the canvas | Publish from Workflow Settings. |
Configure the Step or Form interface and test the automation before publishing. Form field setup is covered in Building a Form Interface.
Publish validation and credential scrubbing: When you submit a template,
Glow validates the selected version and refuses raw API keys, Steps with no
selected action, retired operations, invalid value types, run-breaking graph
defects, bare {{ N }} references on {result} Steps, or workspace member
email addresses in copied fields or form labels. Installing a template strips
source account bindings, secret fields, remote resource pickers, email
defaults, and exposed Custom Variables values automatically.
Publish from Workflow Settings
Save and Submit a Version
Open Workflow Settings on the canvas. Select a saved version (or create a new one) and submit it for publication.
Fill In the Listing Details
Fill in Who’s it for, How it works, Setup instructions, Requirements, and an optional YouTube video URL. You can also click Generate descriptions to draft these fields, which autosave on blur.
Marketplace submissions enter In review and go to the Glow team for approval before appearing in the public gallery. While a new version of an already listed template is in review, the current approved version stays listed and its listing copy and version metadata remain locked in place. Official templates curated by the platform team carry the By Glow publisher badge.
The Versioned Deployment Flow
Open Share → Deploy on the canvas, or use a Deploy entry point on The Deployment Page. This opens a two-step modal.
Basic Info and Interface Selection
In Basic info, verify the automation title, description, and category. Confirm whether it deploys as a Step or Form interface. If you use ✦ Generate descriptions, follow the generation precautions before continuing.
Version and Target Destination
In Version & deploy, pick an existing snapshot under Version name or choose New version to save one with a tag and release notes, then select destinations:
- Marketplace: Publishes publicly to the template gallery.
- Managed clients: Select up to 50 client workspaces per batch (each receives an independent Draft copy). Requires an active Full operational grant with Full workspace scope; see deployment permissions.
- Client-only delivery: Select your target workspaces under Clients and clear Marketplace, which stays independent of client selection.
Review and Deploy
Check the selected version and destinations, then click Deploy. Deploying again to clients creates new copies; it does not update earlier deployments. Review destination resources and account rebinding before testing or activating those copies.
Generating Descriptions
Generate descriptions drafts the description sections and suggests categories for you to review. Glow covers the AI usage for description generation.
The input depends on the entry point:
- From the canvas’s Share → Deploy menu, Generate descriptions summarizes your current Step names and graph structure.
- From Workflow Settings or the Deployment page, it also draws context from your saved Step parameters and sticky notes.
Review the generated summary before publishing to confirm it matches the version you intend to publish.
Review generated copy before publishing. Check that it explains the problem the automation solves, its prerequisites and any actions that change external systems. Add missing details and remove claims the selected version does not support.
Publishing Updates and Unpublishing
Editing the source automation does not update its published version. Save a new version with your changes, then deploy it through Share → Deploy or Workflow Settings.
Submitting a new version sends it for review without changing existing installed copies or client deployments. Once approved, it replaces the previous Marketplace version and clears any Featured mark until reviewed again.
Unpublishing a template: Open Workflow Settings on the source automation and click the Unpublish template icon in the template banner. Archiving the source automation also removes its listing from the Marketplace, while existing installed copies keep running.
Creator profiles
Your name and picture appear on every template you publish. Gallery cards link to the template detail page; the creator’s name on a card is attribution, not a separate profile link.
The name and picture on your account settings are what a reader sees attributed to your work, so those are the pair worth filling in.
Best practices for templates
- Document prerequisites. Avoid team-specific secrets or files that a recipient would not have. List required accounts and resources so recipients can configure their own copies.
- Use descriptive Step names. Names such as
Fetch User Datahelp someone follow the automation. Add Sticky Notes near complex branches to explain why they work that way. - Test each route. Use test data and destinations to check field mappings and expected results. Running a test can still send messages or change records.
- Publish deliberate versions. Save and test a version before publishing it, and describe the changes so existing users can decide what to adopt.
- Run
- Open Share → Deploy on the canvas, select a saved version and destination, and click Deploy
- You should see
- The Deployment page shows the published Marketplace badge or the target client workspaces in the Deployed to column.
What’s Next?
- The Deployment Page: manage publishable automations, including those not yet deployed.
- Versioning: save and review automation versions.
- Importing an Automation: rebuild an n8n workflow or Make scenario in Glow.