Skip to main content
Duplicate workflows to reuse automations across workspaces without rebuilding from scratch. Each copy is independent—you can customize it for the target workspace’s needs.

​
When to Duplicate

​
Duplicate a Workflow

1

Open the workflow

Navigate to the workflow you want to duplicate
2

Open the menu

Click the … menu in the top right corner of the workflow
3

Select Duplicate

Click Duplicate or Duplicate to workspace
4

Choose the target workspace

Select which workspace should receive the copy. You can duplicate to:
  • The same workspace (creates a copy you can modify)
  • A different workspace (where you have manager rights)
5

Confirm

Click Duplicate to create the copy
The new workflow opens ready for customization.

​
What Gets Copied

New copies keep the source workflow’s Who can request audience, replacing the receiving workspace’s automatic default. When you copy to another workspace, Workspace Members refers to members of the receiving workspace. Custom access profiles must have matching profiles in that workspace; if a profile is missing, duplication stops and names the missing profile. Choose a workspace with matching profiles, or promote the profiles to a linked destination before trying again. Updating an existing linked copy keeps the receiving workflow’s audience, approval steps and Require form confirmation setting. Only the name, description and code are pulled.
A workflow that uses a reusable approval procedure is duplicated without that procedure attached, whether you duplicate within the same workspace or to another workspace, so you can attach the right one for the destination. Approval steps built directly into the workflow are copied as-is.
The duplicated workflow starts as a draft. Review the configuration and publish when ready.

​
After Duplicating

​
Check integrations

The target workspace must have access to the same connected applications. If the workflow uses Okta, GitHub, or other integrations, verify:
  1. The target workspace has the integration connected
  2. The integration has the required permissions
  3. Any referenced resources (groups, repos, etc.) are accessible
Workflows will fail if they reference integrations the target workspace doesn’t have. Check the workflow’s connected apps before publishing.

​
Update workspace-specific references

Some values may need updating for the new workspace:
  • Slack channel names or IDs
  • Group names or IDs
  • Email addresses or distribution lists
  • Resource identifiers

​
Reconfigure triggers

Certain triggers need reconfiguration after duplication:

​
Adjust execution scope

Review who should run this workflow in the new workspace:
  • Anyone in the org — Available to help desk agent for all users
  • Workspace members only — Restricted to the target workspace

​
Keeping Duplicates in Sync

Duplicated workflows stay linked to the original. When the source workflow is updated, you can pull those changes into your copy.

​
Pull updates from the original

When the source workflow has new versions available:
  1. Open the duplicated workflow
  2. You’ll see a notification that updates are available
  3. Review the changes from the source
  4. Choose to pull the update or keep your current version
This lets teams benefit from improvements to the original while maintaining their own copy. If Pull update fails, the dialog keeps the error visible. In Catalyst, a failed pull does not publish the update, although it may save a draft.
  1. Read the error and choose Close and fix this workflow to return to your copy, or use the linked source workflow to correct its published content
  2. Correct the reported issue, such as choosing an accessible integration for a custom app alias
  3. Choose Pull update again, then review and publish the staged change

​
When to pull vs. customize

Pull updates regularly to stay current with bug fixes and improvements from the source workflow.

​
Permissions

To duplicate a workflow:
  • To the same workspace — You need edit access to the workspace
  • To a different workspace — You need manager rights on the target workspace
You can only duplicate to workspaces you have permission to manage.

​
Best Practices

Name clearly

Update the name to reflect the workspace or purpose: “IT User Offboarding” vs “HR User Offboarding”

Review before publishing

Check all references, integrations, and settings before making the workflow available

Document changes

Note in the description what was customized from the original

Test thoroughly

Run the workflow manually to verify it works in the new workspace context