One AI workflow for many clients: a main flow and a linked copy for each
Build an AI employee once, give each client a linked copy with its own city, list or address, and improve all of them at the same time by changing only the main flow.
Part of the guide AI employees
To run one AI workflow for many clients, build it once as a main flow, then make a linked copy for each client that holds only what differs for them, such as their city, their list of sites or the address their report goes to. In xMap Flows a change saved in the main reaches every copy within moments, while each copy keeps its own runs, results, budget and settings. One design, many clients, and no hunt through twenty flows when you improve the wording of a prompt.
Consultants, franchise advisers and small agencies often sell the same service to many clients: a monthly rival watch, a weekly list of new businesses, a rating report. This article explains when linked copies fit, how to choose what each copy keeps of its own, how to make and maintain them, how each client sees their results, and the mistakes that cause trouble later. Background on the idea of an AI employee is on AI employees.
When linked copies are the right tool
Linked copies live inside one organization. They suit a business that serves its clients from its own workspace and shows each one a page of results, rather than giving every client a login.
| Your setup | Best way to reuse a flow |
|---|---|
| Clients served from your own organization | Linked copies: one main, a copy per client |
| Each client has its own organization | A flow file exported once and imported into each, or a template page clients set up themselves |
| One client, many cities | Linked copies too, a copy per city |
| Clients who want something quite different | A separate flow; forcing it into a copy causes more work than it saves |
Copies work best when the job is the same and only a few settings differ.
Choosing what each copy keeps
When you make copies, you tick the settings that are each copy's own. Everything else follows the main. The usual ones are offered first:
- the cities or drawn areas in the Area of interest;
- the kinds of place a search looks for;
- who receives the Email, or which Slack channel a message goes to;
- the time the flow runs;
- the client's own list in My data, such as their branches;
- flow variables, for things like the client's name in a report title.
Tick as few as you can. Every extra setting a copy owns is one more thing that will not improve when you change the main.
Making the copies
- Build and test the main flow until you are happy with it.
- Open its ... menu and choose Make linked copies, then tick what each copy has of its own.
- Fill one row per client: the copy's name and its own values. Separate places with semicolons and list items with commas. Or press Paste from a spreadsheet, or take the rows From a table in My data.
- Press Make. If the main is live, you can deploy the copies straight away.
- Open Linked copies in the main's ... menu to see every copy with its values, status and last run.
A main can have up to 200 copies, and a copy cannot have copies of its own.
Keeping them in step
Save a change in the main, such as better scoring instructions or an extra filter, and the Linked copies panel shows it reaching each copy. A copy whose run would now fail, perhaps because the new block needs a setting it lacks, is paused and its owner is told instead of failing silently. Each copy keeps a version from before the change in its History, so you can always see what it ran last week.
In a copy itself, only its own settings can be edited. Anything else asks you to unlink it first, after which it keeps its blocks as they are and stops following the main. From the panel you can also edit any copy's values, and pause or deploy all of them at once, which is useful before a holiday.
Showing each client their own results
Each copy has its own results, so pair it with a client view: a branded, read-only page you make for one client from Results, Shared links. Choose that client's copy, add a note at the top, and send the private link. The page shows the results, a map and the weekly report card, and stops working the moment you stop sharing it.
A made-up example
A franchise adviser in Cape Town looks after twelve independent gyms across the city and nearby towns. Every month each owner wants to know which gyms and studios opened near them and how rivals are rated.
- She builds one main flow: Schedule on the first Monday, Area of interest, Nearby places for gyms and fitness studios within 3 km, Only new, xMap LLM writing a short note on each newcomer, and an Email.
- She ticks two settings as each copy's own: the point in Area of interest and the Email's recipient.
- She pastes twelve rows from her client spreadsheet: gym name, address, owner's email. Twelve copies appear, all live.
- In month two a client asks for ratings to be included. She adds that once to the main's instructions; all twelve copies use it from their next run.
- Each owner also gets a client view with their map and report card.
Her monthly upkeep is one flow, not twelve.
Mistakes to avoid
- Editing a copy to try an idea. Try it in the main, or in a test duplicate, so every client benefits or nobody does.
- Giving copies too many settings of their own. If half the flow varies, the clients need different flows.
- Deleting the main without thinking. The app asks whether to unlink the copies, so they carry on as ordinary flows, or archive them too.
- Forgetting budgets. Each copy has its own monthly budget; set one per client so a busy area cannot use another client's share.
Questions
What happens to the copies when I change the main flow?
The change reaches every copy within moments. Each copy keeps its own settings, keeps a version from before the change, and is paused with its owner told if the change would make its next run fail.
Can I change just one client's copy?
Only the settings marked as that copy's own can be changed. Any other change asks to unlink the copy first.
How many copies can one flow have?
Up to 200 linked copies, each with its own runs, results and budget.
Can copies be in different organizations?
No, linked copies stay in the main's organization. For clients with their own organization, export the flow as a file or share it as a template page.
Do clients need an account to see results?
No. A client view is a read-only page opened from a private link, and you can stop it at any time.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates