Copy and paste router paths (rules + actions) across routers
M
Michael Fountain
Routing configuration can't be reused across routers. Setting up a new router with logic similar to an existing one means manually rebuilding every condition and action from scratch, including field update actions, which must each be configured individually with no way to copy them within or across routers.
Requested behavior: Let admins copy a router path, the full block of matching conditions plus its actions (routing rules, field updates, and other node actions), and paste it into another node in the same router or into a different router as a starting point. Copy-paste should work at the path level so common logic transfers in one step rather than being rebuilt action by action.
Why it matters: Teams often configure logic in one router and want the same or near-identical setup in another. Rebuilding it manually wastes time and introduces inconsistency between routers. Copy-paste reuse of paths and their actions is a basic efficiency expected by anyone managing multiple routing configurations, and it keeps field updates and rules consistent across the org.
G
Grace Halverson
Copy and paste nodes and router paths for concierge would be such a time saver! I know it's already possible on chilichat, but would be awesome for routers as well! For example, some product release routers we want extremely customizable paths based on hidden form fields that need to be changed per release. This is not scaleable currently, but could be much easier if copy and paste were allowed for admins!
Taylor Jennings
Merged in a post:
Copy and paste router paths within Orchestrator Flow
K
Kevin Konkle
The ability to copy, cut, paste paths within the orchestration flow. Often times, adding an action upstream in the flow causes the automatic decision branch to apply the wrong downstream branch. There's no way to move existing paths around without having to re-build it from scratch.
Taylor Jennings
Merged in a post:
Copy-Paste Functionality for Field Updates in Router
Taylor Jennings
Field update actions in the router must be configured individually each time. There is no way to copy an existing field update and paste it elsewhere in the same router or a different one.
Admins should be able to copy field update actions within the router and paste them into other nodes or routers, so common configurations don't have to be rebuilt from scratch.
Manually recreating field update configurations across routers is tedious and error-prone. Copy-paste functionality reduces setup time and keeps configurations consistent.
Taylor Jennings
Merged in a post:
Clone Button for Routing Paths
P
Phillip Testa
Routing paths must be built from scratch each time. There is no way to duplicate an existing path and modify it, even when the new path is nearly identical to an existing one.
Admins should be able to clone an existing routing path as a starting point for a new one, preserving all conditions and actions so only the differences need to be changed.
Recreating similar routing paths manually is time-consuming and error-prone. Cloning reduces setup time and ensures consistent structure across related paths.
Taylor Jennings
Merged in a post:
Copy and Paste Routing Rules Across Routers
R
Russell Abdo
Routing rules cannot be reused across different routers. Setting up a new router with similar logic to an existing one requires manually rebuilding every condition and action from scratch. Admins should be able to copy routing rules from one router and paste them into another as a starting point, so common logic doesn't have to be rebuilt repeatedly. Manually recreating identical or near-identical routing rules across routers wastes time and introduces inconsistency.