Pushing Automations to Clients
Use Deploy automation in your console to copy one or more automations into one client workspace. Each source uses its current automation definition, not a selected saved version. The source does not need to be Live to copy it. The new copies arrive in Draft with triggers disabled; your originals remain unchanged.
- Use it to
- Copy the current canvas definitions of one or more automations into a single client workspace
- Find it
- Clients → Overview → Deploy automation
- Limits
- One target client workspace per push · Requires an active Full operational grant with Full workspace scope
- Output
- Inactive Draft copies in the client workspace plus a deployment receipt listing missing connections and empty variables
- Instead
- Workspace Deployment (when rolling out a specific saved version to up to 50 clients)
This console action is copy-only. It is separate from both the admin copy/move wizard and saved-version Workspace Deployment.
Choose a Deployment Method compares this Admin Push with saved-version Workspace Deployment.
Pushing needs a full-operational, full-workspace grant. Read-only access cannot create client automations. If the client approved your practice for selected automations only, pushing adds a new automation outside that agreed list and is refused (MSP_SCOPE_INSUFFICIENT). Request full-workspace access and have the client’s Admin consent to the new grant before pushing into their workspace. See Access Tiers & Scope.
The Push Flow
Start the push
In your console, click Deploy automation.
Pick the automations and client
Select the source automations in Automation, then choose one client workspace. To deliver to another client, repeat the process for that client.
Check existing copies
If Glow reports an existing copy, inspect it before confirming another deployment. Pushing never updates an existing client automation; confirming creates a second independent copy. Edit the client-owned copy directly when you want to update an existing automation.
Confirm and deploy
Click Deploy automation. Glow checks all selected sources before copying them, then creates the client copies sequentially. The dialog does not provide the admin copy/move wizard’s per-file or per-variable review.
Review the results
Read the deployment receipts, including counts of missing connections and empty variables. Copied automations arrive inactive while your source automation stays unchanged. Both workspaces record an activity-log entry, and client Admins are notified when the transfer completes. Open each copy in the client workspace to finish configuration and test before activation.
Partial success is not rolled back. If some automations deploy and others fail, successful copies remain in the client workspace. Use the dialog’s retry option for the remaining work rather than starting a fresh deployment of everything. If you lose the result, check the client workspace before confirming another copy.
Review the Client Configuration
Preflight runs in the background without writing client copies. All selected sources must pass before copying starts. Use the deployment receipts and the client copies to verify each resource below.
| Resource | What happens on push | Action required in client copy |
|---|---|---|
| Connected accounts | Auto-binds only when the client has one matching account in total and it is healthy. Your accounts never transfer. | Have the client connect or select the right account when missing, unhealthy, or ambiguous across several accounts. |
| Variables and secrets | Source values never transfer. Existing target values stay client-owned; missing keys are created empty. | Check empty-variable counts in the receipt and have the client fill in missing values. |
| Team files | Referenced team files can be copied with the automation without a per-file checklist. | Review source files before deployment and confirm the copied files in the client workspace. |
| Sample data | Captured Step samples are stripped from cross-workspace copies. | Collect fresh test data in the client workspace before testing. |
| Subflows and AI Agents | Child automation references, Agent tool bindings, external MCP tools, and knowledge sources are removed. | Deploy child automations separately, rebind Agent tools and knowledge to client resources, and review approval policies. |
- Run
- Deploy one automation to a client workspace and review the deployment receipt.
- You should see
- The new copy appears in the client workspace in Draft with triggers disabled.
What’s Next?
👉 Your Console →: monitor the automations you deployed.
For a saved-version rollout, return to Choose a Deployment Method. Review Impersonation if you need delegated entry into a client workspace.