Share a flow with a link

The fastest way to put a flow in someone else's hands is a share link: a URL that opens a hosted chat with your flow. The recipient doesn't need a ZeroWidth account, a workspace seat, or any setup — they click and start talking.

1. 1
   Open the share dialog

   On the flow's detail page, click Share. The dialog is titled "Share with a guest."

2. 2
   Create a link

   Pick the Link delivery method, give it a label under "Who's this for?" (so you can tell your links apart later), and optionally set an expiry — anywhere from 1 to 365 days, or leave it open and revoke by hand. Create the share.

3. 3
   Send the URL

   You get a guest URL like https://workbench.zerowidth.ai/s/<token>. Anyone with the link can chat with your flow's latest published version — no guest account and no saved history, so each session starts fresh.

Good to know

• Guest turns are real runs. Every message a guest sends is a flow run: it counts against your workspace's spend and shows up in the flow's Runs tab like any other run. A public link is a real cost surface — set an expiry, and don't share it wider than you mean to.
• Revoke anytime. Kill a link from the same dialog; the URL stops working immediately. You can have up to 20 live links on one flow.
• It always tracks the latest published version. Re-publish the flow and existing links serve the new version automatically — no need to re-share.

The same share, as a webhook

The share dialog's fourth method, API, gives you a URL to POST to instead of a page to open. Send { "input": "…" } and you get { "output": "…" } back — one turn, no account and no API key, because the share token itself is the permission. It's the quickest way to wire a flow into Zapier, n8n, a cron script or a Slack workflow step.

It carries the same caps as the chat link, and revoking the share kills both.

curl -X POST https://api.zerowidth.ai/guest/workbench-shares/<token>/invoke \
  -H "Content-Type: application/json" \
  -d '{"input": "Summarize this ticket: ..."}'

For anything that needs conversation history, versions or per-key budgets, use the run API with a real key instead.

Other ways to share

The same share, different surface: