The Deployment Page
Switch automation interfaces, manage saved versions, and deploy automations to the Marketplace or client workspaces from one table. Deployment lists every publishable automation in your workspace, including those not yet deployed.
- Use it to
- Switch automations between Step and Form interfaces, manage versions, and deploy to the Marketplace or managed client workspaces from one table
- Find it
- Left sidebar → Deployment → Deploy workflow
- Limits
- Up to 50 managed client workspaces per deployment batch (requires an active Full operational grant with Full workspace scope)
- Output
- Public Marketplace listing and/or independent Draft copies in selected client workspaces
- Instead
- Direct Admin Push (/msp/choosing-a-deployment-method) when pushing an automation straight to a single client workspace
Open Deployment in the left sidebar. Use Search interfaces to filter rows, or click Deploy workflow in the header to pick an automation and open the versioned deployment modal. In an empty workspace, the preview rows are examples rather than published automations.
Deploying to Clients? If you manage multi-tenant clients as a consultancy or MSP, Choose a Deployment Method compares this versioned deployment route with the one-client direct Admin Push flow.
Understanding the Deployment Table
The Deployment table lists every publishable automation in your workspace alongside its active interface type and distribution status:
| Column | What it tells you | Operational Actions |
|---|---|---|
| Interface | How the automation is consumed: Step or Form. | Click the dropdown to switch interfaces. |
| Automation | The automation name, latest manual version, and interface detail (form field count or workflow step). | Click the automation title to open the visual canvas. |
| Author | The workspace member who authored the automation. | Identifies team ownership and maintainers. |
| Last edited | Relative timestamp of the most recent change. | 2h ago, yesterday, 3d ago. |
| Deployed to | Where the automation is actively published. | Shows Deploy (unpublished), Marketplace badge, or client tenant logos. |
Find unpublished automations: Use the Deploy link in the Deployed to column to start publication. An unpublished automation is not necessarily ready to distribute; review and test it first.
Selecting an Interface: Step vs. Form
See Choosing the Right Template Type for the difference between an editable Step template and a Form template. The table provides controls for changing the mode and opening form setup.
Switch Interface Mode
Click the Interface chip in the table row and select Form or Step.
Configure Form Fields (Form Mode)
If selecting Form on an automation without configured inputs, click Set up form in the No fields defined notice. For any Form row, you can also open More (⋮) → Set up form…. The form builder drawer opens beside the table. Follow Building a Form Interface to select fields and configure defaults.
The Versioned Deployment Flow
Follow The Versioned Deployment Flow for full step-by-step details. From the Deployment page, Generate descriptions uses your saved Step configuration and sticky notes to draft the listing; see Generating Descriptions.
Check the destinations before deploying. For client-only delivery, clear Marketplace and confirm each client has an active Full operational grant with Full workspace scope. Client deployment creates independent Draft copies rather than updating earlier ones.
Credential Isolation During Deployment
Review the source fields and the destination accounts separately:
Automated credential stripping: Glow removes source account bindings and recognized credential fields automatically during deployment. Store environment-specific tokens or URLs in workspace Variables and Secrets rather than placing them in plain text fields.
- Workspace resources: Configure required secrets, variables and files in the destination. Do not assume a source reference makes the resource available there.
- Client-owned execution: Target workspaces receive independent automations with copied Step settings, not blank Steps.
- Account rebinding: Automatic binding happens only when exactly one healthy matching account exists in the target workspace. Otherwise, select or connect the intended account manually before testing.
- Pre-Activation Review: Automations arrive in Draft mode so workspace Admins can review connections before switching to Live.
- Run
- Open Deployment in the left sidebar and click the Interface chip or Deploy on a publishable automation row
- You should see
- The row switches between Step and Form mode, or opens the versioned deployment modal for that automation.
What’s Next?
- 👉 Form Templates →: Select exposed fields and configure default values.
- Publishing Templates: Publish a version to the Marketplace or deliver copies to managed clients.
- Choose a Deployment Method: Compare workspace version deployment with direct MSP Admin Push.