One flow for many cities or clients: linked copies
Build an AI employee once, run a copy for each city, client or team, and change them all from one place.
By the xMap team · Updated
A linked copy is a flow of its own, with its own runs, results, budget and owner, whose blocks follow another flow, its main. Change the main and every copy changes with it; each copy keeps only the settings you chose to be its own, such as its city, the kinds of place, who to email or which Slack channel to post to.
Make linked copies
- Open the flow and press ..., then Make linked copies.
- Tick what each copy has of its own. The usual ones (cities, who to email, the time it runs) are offered first.
- Fill one row per copy: its name and its own settings. Separate places with ; and lists with commas. Or Paste from a spreadsheet (a heading row matches the columns), or take the rows From a table in My data.
- Press Make. When the main flow is live you can deploy the copies at once.
Keeping them in step
- Every change you save in the main reaches its copies within moments: Linked copies in the main’s ... menu shows how far it got.
- When a change alters what a copy runs, the copy keeps a version from before it in History (at most one every 10 minutes) and Activity says it took the change; moving blocks around changes nothing in the copies.
- A copy that is live stays live. If the change would make its next run fail, it is paused and its owner is told.
- A setting whose block you removed from the main is dropped from the copies, and the panel says so. A setting new in the main can be made each copy’s own from the panel.
Changing a copy
In a copy, only its own settings change (in its blocks, or with My settings in the band at the top). Anything else asks you to Unlink this copy first: it then keeps its blocks as they are and no longer follows the main. From the main’s Linked copies panel you can edit any copy’s values, unlink it, and pause or deploy all of them at once.
Good to know
- Only people who may change the main can make copies. A copy belongs to whoever made it and starts with the main’s sharing.
- While a copy is live, changing the main’s blocks needs the right to deploy.
- Someone else’s personal account is never copied into your copy.
- Deleting the main asks whether to unlink its copies (they carry on as ordinary flows) or archive them too.
- A flow can have up to 200 linked copies, and a copy cannot have copies of its own.