Working Together

This optional tutorial shows how two people can edit the same workflow at once, see each other’s cursors and divide the work without creating separate copies. It continues from the workflow built in Tutorial 3, but nothing else in the learning sequence depends on completing it.

🎯

What you will learn: Sharing a workflow, editing alongside someone in real time, and who can see what.

This one needs a second person. If you are working alone, read it now to know what is available and come back when you have someone to build with — nothing later in the docs depends on having done it.

Step 1: Check they can get in

Your colleague needs to be in this workspace already. The link alone does not grant access: it opens the workflow for someone who is already a member, and shows nothing to anyone else.

If they are not a member yet, invite them from the workspace menu → Manage team. See Setting Up Your Team for the roles available and what each one may do.

If you have restricted this particular workflow, check its visibility too — see Workflow Visibility and Sharing.

Copy the URL of your workflow from your browser’s address bar and send it to your colleague.

When they open it, their avatar appears in the top right corner and you will see their cursor moving across the canvas in real time. Anything either of you changes shows up for the other without a refresh.

Step 3: Split the work

The lead router from Tutorial 3 divides neatly between two people, which is the point of building it together rather than describing it afterwards.

Take the routing yourself

Configure the Conditions step: the rules that decide which region a lead belongs to. That is the part that needs to know how the workflow is wired.

Give the copy to whoever owns it

Your colleague clicks the four Slack steps and writes the message for each. That is the part that needs to know what Sales actually wants to say, which is rarely the same person.

You are both editing the same workflow at the same time, so there is no copy to merge afterwards and no screenshot to describe.

Step 4: Save a version before you leave it

Once the two of you are happy with it, save a named version. That gives you a point to return to if the next round of edits goes wrong — see Versioning for how restoring one behaves.

What’s Next?

That covers the tutorials. The next step is building something for your own work.

Cookbook — worked recipes covering real business scenarios, with settings to copy.
Real-Time Editing — what multiplayer does when two people change the same step at once.
Glossary — look up any term these tutorials used.