Concepts

Community Flows

Share a flow you built with everyone — every submission is secret-scanned, AI-reviewed, and approved by a person before it goes public.

Sharing a flow

Open the flow and click Submit in the canvas toolbar; it stays greyed out until the flow has a node. The first time you pick a screen name — pseudonymous, so you are credited without your email ever being shown. Publishing needs an activated license; a trial can build and run flows but not share them.

Submit to Community: your screen name, what gets uploaded for review, and the destructive-action notice.
Submit to Community: your screen name, what gets uploaded for review, and the destructive-action notice.

The scan and an AI review run on their own; a person approves. Automated checks can only reject, never publish. You get an "Under review" confirmation, then an email either way — when it goes live, or when it could not be published. Sharing is capped at 3 flows a day, 20 a month, and 5 awaiting review at once.

Submission requirements

The catalog is small on purpose: every flow in it should be something a stranger can add and trust. The review checks for these.

  • It runs on a fresh Mac. Nothing but Watchflows: no extra tool, library or helper app. Where only the person adding it can make a choice, such as a folder, a calendar or an account, put {{NEEDS_INPUT: what to choose}} in that field. Your own paths and names never ship.
  • It does one thing, all the way. A good flow ends with something you can see: a file moved, a note written, a message sent. One that stops at a picker or a transform nothing reads needs one more node, and the review says which.
  • It is different from what is already there. A catalog flow with one setting changed is not a new flow. If you improved an existing one, say which and what changed.
  • Scripts are allowed, and read line by line. A flow with a script, or one that can modify your Mac, is marked on its page, arrives switched off and asks before its first run. One that downloads and runs code, asks for an admin password, hides what it does or reaches for credentials is blocked, along with the account that sent it.
  • Paid and third-party services are fine, declared. A flow built on Linear, or any service with its own account, is welcome. Its page says so.
  • No secrets, ever. Your providers and keys stay in your Keychain and never upload. A real value in a secret field fails the scan outright; anything that looks like a key, anywhere in the flow, waits for a person to look.
  • It is yours to give, and you give it. Submitting places the flow in the public domain. Anyone can add it, change it and share the change. Your screen name stays on the card.
  • Anyone can report a flow. If a flow does something its page did not say, tell support@watchflows.app. A person reads every report, and a flow that should not be in the catalog comes out.

Only the flow itself travels: name, nodes, connections, node settings, canvas background. Home-folder paths are redacted (/Users/yourname becomes /Users/«USER»), run history and AI cost data are not in the export at all, and a Public Webhook node's channel id and secret are stripped on the way out.

Good to know

Adding one costs nothing. Browse and add in the app, offline, from a catalog baked into Watchflows. A flow's AI nodes arrive without the author's provider and model, so it runs on yours and you pay only for your own runs.

Published is published. A takedown removes a flow and blocklists it, and a submitter can be banned or their data erased on request — but treat anything you share as public from the moment it is approved.