Share and publish
Publish an article
Write a public tutorial, attach workflow snapshots, and publish a reviewed revision.
Articles explain a workflow’s purpose, setup, and behavior. Public readers can read an article and download its attached workflow files without signing in. Execution happens in their own imported copy in the app.
Publishing roles#
- User: use the app, read public articles, and import or export workflows.
- Author: also create drafts and publish, edit, or unpublish their own articles.
- Admin: also manage author access and unpublish articles.
New accounts start as Users. Author access is granted explicitly by an Admin. Publishing roles are separate from subscription plans. Author access does not grant permission to change official docs or mark a workflow as an official example.
Create a useful draft#
Provide a descriptive title, summary, stable URL slug, and a few relevant tags. Start the body with the outcome and who the tutorial is for. List prerequisites and setup instructions before the steps that depend on them.
Use headings for stages, code blocks for code or JSON, and images where they clarify a result. Include what a successful run should produce and how readers can verify it.
Attach a workflow snapshot#
Download the workflow from the app, then attach its file in the editor. Give the attachment a useful caption. Review the graph and parameters, and remove private literal values before publishing.
The attachment is a snapshot. Editing the original app workflow does not update the article. To share a newer version, replace the attachment and republish.
Preview, then publish#
Preview the draft, check its links and workflow setup, then publish it. Changes to an already published article stay in the draft until you republish. Readers continue seeing the last published revision while you work.
Readers can inspect a public workflow without running it, download the JSON, or choose Use this workflow to import a copy. Describe every connection and input they need before their first run.
See import and export for the portable-file contract.