Share a routine as a page

Open Interface and build the page visitors should see: a heading, the required fields, a run button and the result blocks. Test it in preview, then open Publish. The dialog checks the workflow and the address. Only after successful publication should you share the public address it displays; the editor's Share action does not publish this page.

The address is part of the point. It is short, it says what the routine does, and it works anywhere a link works: a message, an email, a group chat. You are not sending instructions or a file to figure out. You are sending a place people can visit.

Anyone with the link. They do not need to install anything, and they do not need an account. A phone browser is enough. That matters more than it sounds: the people who would benefit most from your routines are often the ones who would never set up a tool themselves.

You stay the owner. The page runs your routine, built your way, with your steps. Visitors use it; they do not edit it. If you improve the routine later, publish it again and the page serves the new version at the same address. Everyone who saved the link gets the better routine without doing anything.

Take a small, real case: notes after a call. Build a routine with one Cyber Brain step that takes rough notes, tidies them into a clear summary with decisions and to-dos, and saves the result to Notion. On the canvas, that is two or three steps. Shared as a page, it is a text box and a button.

Now give the link to the three people you meet with every week. After each call, whoever took notes pastes them in and taps run. The tidy summary lands in the shared notes, formatted the same way every time. Nobody installed anything. Nobody learned a tool. One person built it once.

You can stop publishing from the Publish dialog. Use its unpublish control and wait for confirmation before treating the public page as unavailable. The workflow itself stays in your workspace. Unpublishing is different from deleting the workflow or merely stopping an execution.

There is also a quieter way to share: save the routine as a file and send it directly. The other person loads it into their own canvas and can change whatever they like. Use the page when people should use your routine. Use the file when they should own their copy.