Skip to main content
Duplicate workflows to reuse automations across teams without rebuilding from scratch. Each copy is independent—you can customize it for the target team’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 team
4

Choose the target team

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

Confirm

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

​
What Gets Copied

The duplicated workflow starts as a draft. Review the configuration and publish when ready.

​
After Duplicating

​
Check integrations

The target team must have access to the same connected applications. If the workflow uses Okta, GitHub, or other integrations, verify:
  1. The target team 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 team doesn’t have. Check the workflow’s connected apps before publishing.

​
Update team-specific references

Some values may need updating for the new team:
  • 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 team:
  • Anyone in the org — Available to help desk agent for all users
  • Team members only — Restricted to the target team

​
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.

​
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 team — You need edit access to the team
  • To a different team — You need manager rights on the target team
You can only duplicate to teams you have permission to manage.

​
Best Practices

Name clearly

Update the name to reflect the team 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 team context