Working Together

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

At a glanceVerified in app · Oct 30, 2026

Use it to: Invite a colleague onto the same canvas, follow their live cursor, divide Step edits in real time, and save a named version
Find it: Canvas header → Share → Invite to canvas · More (⋮) → Documentation & history
Cost: 0 Step credits (editing and saving versions in Draft runs no Steps)
Limits: Requires Admin, Manager, or Member role with access to the automation (Viewers have read-only canvas access)
Output: Synchronized canvas edits and a named, restorable checkpoint in the History tab

🎯

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

This one needs a second person. Working alone? Skip to Use Cases & Examples and return when you have someone to build with. Nothing later in the docs depends on this tutorial.

Step 1: Check they can get in

Open the lead router from Tutorial 3 in Draft with its test destinations selected. You only need to edit and save for this tutorial, not run the automation.

Both of you need an Admin, Manager, or Member role and access to the automation (a Viewer cannot edit, and the link alone does not grant access). Invite a colleague directly from Share → Invite to canvas or via Members and invites; see Setting Up Your Team.

Copy the URL of your automation from Share (or your browser’s address bar) and send it to your colleague.

When they open it, their avatar appears in the top right corner and their cursor moves across the canvas in real time. Click their avatar to Follow their camera view; edits appear immediately without refreshing.

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 automation 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.

Check each other’s work before moving on. Ask your colleague to open Conditions and read back one routing rule. Open a Slack Step yourself and confirm their revised message. Both changes should be visible without refreshing or exchanging copies.

Step 4: Save a version before you leave it

Once the two of you are happy with it, open More (⋮) → Documentation & history and save a named version. That gives you a point to return to if you need to undo later edits. See Versioning for how restoring one behaves.

You have finished when both of you can see the agreed rules and messages, and the named version appears in the History tab. Leave the automation in Draft. Before using the revised messages with real leads, repeat Tutorial 3’s route tests.

Verify it works

Run: Open the shared draft canvas alongside your colleague, edit a Conditions rule and a Slack message, then save a named version under More (⋮) → Documentation & history.
You should see: Both cursors and edits appear immediately without refreshing, and the named version is listed in the History tab.

What’s Next?

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

Use Cases & Examples: worked automation examples covering 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.