Templates and Reuse

Glow provides distinct mechanisms for reusing, sharing, and executing automations depending on who will operate the workflow:

Pre-built workflow blueprints from the Marketplace. Fork the full editable canvas into your workspace and customize steps.

1. Step Templates (Marketplace)

Standalone form execution wrappers. End-users fill in input fields and run workflows without touching the canvas or credentials.

2. Form Interfaces

Centralized table to manage workflow interfaces, snapshot semantic versions, and push updates to client workspaces.

3. The Deployment Hub

Templates vs. Interfaces: Key Distinctions

It is important to understand the fundamental difference between Marketplace Templates and Workflow Interfaces:

Concept	What It Is	Who Uses It	Canvas & Credentials
Step Template (Marketplace)	A cloneable workflow blueprint in the public or team library.	Workflow Builders: Users who want to fork, edit, and maintain the automation.	Full canvas copied; forker connects their own app credentials.
Form Interface (Canvas / Deployment)	A front-end form runner built on top of an active workspace workflow.	End-Users / Clients: People who simply submit requests or data to trigger the run.	Canvas completely hidden; securely uses the author’s workspace connections.
Chat Interface (Chat Trigger)	A conversational assistant interface (hosted web page or Slack bot).	Chat Visitors & Teammates: People who converse with the workflow interactively.	Canvas hidden; uses workspace connections and returns AI responses.

Zero Credential Sharing: When publishing a template to the Marketplace or deploying to a client workspace, third-party API keys and OAuth credentials are never exported. Deployed workflows run securely using the destination workspace’s authorized connections.

The Public Marketplace

Explore pre-built workflows designed by the Glow community and certified partners:

🌍

Public Template Gallery: https://app.getglow.ai/templates/

A template's page in the Marketplace: its name and version, a Use template button, the steps it contains, and panels describing what it does, who it is for and what it needs. — A template's page previews its steps, category, required app connections, and interface type before you fork it.

What’s Next?

👉 Step Templates →: Browse, fork, and publish editable canvas blueprints.
Form Templates: Turn any workflow into an interactive form runner for non-technical users.
The Deployment Page: Manage semantic versions and distribute workflows across client workspaces.
Importing & Exporting Workflows: Import existing automations from n8n or Make.