Upgrade a Workflow in Place

Replace a running workflow with a new version without changing its URL or losing its data: what carries over, what you move, and what you redo.

Written By Philippe

Last updated About 1 hour ago

Upgrade a Workflow in Place

A published version never changes. Two things that make a running workflow live outside the version: who calls it (a permalink or a hosted-chat slug) and what it remembers (your data tables). Move the first and reuse the second, and you swap the version underneath without changing callers or moving data.

Steps

Step	Action
1.	On version 1, open the URLs tab and make its permalinks once (Make for all webhooks). Give those permalinks to your callers, not the version's own links. See Keep One Permalink Across New Versions
2.	Get version 2 from the same Builder: publish it if you are the Builder, or buy it. Its Data Table nodes must use the same table id (or the same table name, in by-name mode). See Data Table Node
3.	While version 2 is still off, copy version 1's settings to it: open version 2's Settings tab, choose Copy from…, pick version 1 and choose Copy settings. This copies your instance variables, your saved credential connections and your billing choice. A line next to the button names version 1 and lists what it copied, what it skipped (a variable or credential slot version 2 no longer has) and what you still fill in. With version 2 turned on, the button is disabled and the page says to turn it off first
4.	Turn version 2 on. Its billing is the copied choice; change it here if you want. Then fund its workflow balance
5.	Move the permalinks to version 2: open its URLs tab, choose Move all here from… and pick version 1. The line that follows says how many moved. Move back undoes it
6.	If the workflow has a hosted chat, move its slug to version 2's chat trigger
7.	Withdraw the balance left on version 1
8.	Turn version 1 off

Do step 8 last. While a workflow is off, a call to its own link or to a permalink that still points at it is refused with "Workflow is deactivated. Reactivate it to execute." Move the permalink first, or turn the workflow back on.

Deleting a permalink that you moved from another version loses that address: making a new permalink gives a different one, and callers of the old address get 404.

Through MCP, the same steps use create_permalinks on version 1 once, then copy_instance_settings (from and to), activate_service, fund_budget, move_permalinks (from and to), rebind_chat_slug, withdraw_budget and deactivate_service. delete_permalink retires one permalink by id.

What Carries Over

Item	What happens
Data tables	Automatic when version 2 uses the same table ids (or names)
Builder's default credentials	Automatic
Caller's prepaid balance	Automatic. It is per wallet
Permalinks	One step: move them all to version 2
Hosted-chat slug	One step: move it to version 2's chat trigger
Saved credential connections	One step: copy settings from version 1
Instance variables	Same step: copied with the settings; fill any variable version 2 added
Billing choice	Same step: copied with the settings
Workflow balance	One step each: withdraw from version 1, fund version 2
Run history	Stays on version 1. Your account-wide run list shows both
Chat history	Stays on version 1

Limits

A table id you did not use before gives a new, empty table.
Tables are shared by every workflow from the same Builder, in the same wallet, on the same chain. A different Builder or chain has different tables.
When you sell a workflow, its tables stay with you. See What Transfers When You Sell Your Workflow.

Was this helpful?

Still need help? Ask the team