When to Duplicate
| Scenario | Example |
|---|---|
| Same workflow, different teams | IT and HR both need a user offboarding workflow |
| Template for variations | Base “send report” workflow customized per team |
| Testing changes safely | Copy production workflow to test modifications |
| Sharing best practices | Replicate a successful workflow to other teams |
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
What Gets Copied
| Copied | Not copied |
|---|---|
| Workflow code and logic | Run history |
| Name and description | Version history |
| Input configuration | Published state (starts as draft) |
| Approval settings | Schedule (must be reconfigured) |
| Execution scope setting | Webhook URL (new one generated) |
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:- The target team has the integration connected
- The integration has the required permissions
- Any referenced resources (groups, repos, etc.) are accessible
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:| Trigger type | After duplication |
|---|---|
| Manual | Works immediately |
| Scheduled | Must set up schedule again |
| Webhook | New webhook URL generated—update external systems |
| Event-triggered | May need to reconfigure event filters |
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:- Open the duplicated workflow
- You’ll see a notification that updates are available
- Review the changes from the source
- Choose to pull the update or keep your current version
When to pull vs. customize
| Scenario | Recommendation |
|---|---|
| Source workflow fixed a bug | Pull the update |
| Source added a feature you need | Pull the update |
| Your team needs different behavior | Keep your version and customize |
| Source changed something that breaks your setup | Keep your version |
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
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