Choose a Deployment Method
Copy automations into client workspaces using either live canvas definitions or an approved saved version. Choose your deployment path based on the source version and the number of client destinations.
- Use it to
- Compare Admin Push (current canvas definition to one client) and Workspace Deployment (saved version to up to 50 clients)
- Find it
- Clients → Overview → Deploy automation (Admin Push) or Left sidebar → Deployment (Workspace Deployment)
- Limits
- Requires Full operational grant with Full workspace scope · Up to 50 client destinations per Workspace Deployment batch
- Output
- A new independent Draft automation copy in each selected client workspace
- Copy one or more automations into one client workspace from Clients → Overview.
- Uses the current canvas definition rather than a saved version.
- Runs background preflight and reports missing connections and empty variables in receipts.
- Roll out an approved saved version to up to 50 client workspaces from Deployment.
- Later canvas edits do not alter the deployed Step snapshot.
- Does not require direct membership in the destination client workspaces.
Compare the two paths
| Decision | Admin Push | Workspace Deployment |
|---|---|---|
| Entry point | Deploy automation in Clients → Overview | Deployment in your workspace sidebar |
| Source | Current definitions of selected automations | A saved version you select |
| Destination | One client workspace | One or more selected client workspaces |
| Review | Background preflight, then deployment receipts and configuration review in each copy | Choose the approved version and destinations in Deployment |
| Best fit | Delivering current automation definitions to one client | A controlled rollout from a known version |
| Result | A new inactive client copy for each selected source | A new independent Draft copy in each selected workspace |
Neither path updates an existing client automation. Treat every delivered copy as independent, and finish its client-owned connections, variables and test data before making it Live.
Client deployment creates copies directly in the selected client workspaces. Marketplace publishing is a separate destination in Workspace Deployment, not a prerequisite for client delivery. For a client-only rollout, leave Marketplace off; do not publish a template merely to deliver a client copy.
Use Admin Push
Choose Admin Push to copy one or more current automation definitions into one client workspace. You need console access and a source automation available to you in your practice’s workspace; the grant requirements below apply to the destination. This uses the current canvas configuration, not a selected saved version; the source does not need to be Live. The console checks the sources in the background before copying; it does not show a detailed per-file or per-key preflight. Review the deployment receipts and complete the client copies before activation.
👉 Follow Pushing Automations to Clients →
Use Workspace Deployment
Choose Workspace Deployment to deliver a saved version to selected clients. You need membership in the MSP-enabled source workspace and permission to edit the source automation, without needing a console-admin role or direct membership in each client workspace.
- Choose the version: In Version & deploy, pick a manually saved version under Version name (the newest manual version is preselected; automatic AI checkpoints are excluded). Deployment applies the dialog’s name, description, and interface settings to that snapshot without changing its version title or notes.
- Choose the destinations: Select up to 50 eligible client chips per deployment under Clients; split larger rollouts into batches.
Selecting clients does not turn off Marketplace. Switch it off under Deploy to for a client-only delivery.
👉 Follow the Deployment Page →
Before either deployment
- Confirm an active, unexpired Full operational grant with Full workspace scope for each client. Both paths create new automations, so selected-automation grants are insufficient. A broader grant requires a new request and client consent.
- Save and test the source you intend to deliver.
- Keep client-specific values in workspace variables or secrets rather than embedding them in Step fields.
- Plan to connect client-owned accounts and collect fresh test data in the receiving workspace.
- Inventory Subflows, AI Agent tools, and knowledge sources. Both routes remove these source bindings; complete the client copy before testing.
For an end-to-end handoff, follow Your First Client Automation.
- Run
- Check the target client's grant in Clients → Settings → Client access before starting a push or deployment
- You should see
- The client holds an active Full operational grant with Full workspace scope, allowing new Draft copies to be created.
What’s Next?
👉 Pushing Automations to Clients →: follow the console’s current-definition copy procedure.
For the saved-version route, follow Workspace Deployment. Review what may cross workspace boundaries in How Multi-Tenancy Works.