An n8n-style automation graph, written as a Markdown file. Nodes, edges, credentials, and checkpoints — all plain text.
release_hook
Starts the workflow when an external service sends an HTTP request.
Inputs:
Method
POSTPath
Output:
build
Call an external API and use the response in the workflow.
Inputs:
Method
POSTURL
Body
Output:
notify
Post a message to a Slack channel.
Inputs:
Channel
#releasesMessage
Output:
Slack: Post Message
Write nodes as Markdown
An @automation block: a trigger, a list of nodes, and connections between them.
Arg0 parses the graph
JSON items flow node to node — filters branch, loops batch, checkpoints pause for a human.
Render or run it
The same file drives the visual canvas and the executor — no second source of truth.
In practice
A real release, end to end — the flaky parts retry, the risky parts pause for you.
A tag fires it
Push v1.0.22 — your GitHub tag webhook hits trigger.webhook and starts the run. No clicking through a CI dashboard.
Flaky parts retry, not die
If the Electron CDN drops the download mid-build, the [on_error] edge routes to a cleanup/retry branch instead of a dead run.
Proof before install
codesign --verify, spctl, and stapler validate run as their own node — the build must be signed and notarized before anything moves.
You get the last word
checkpoint.manual pauses the graph. Approve from desktop or your phone — only then does it copy into /Applications and smoke-test.
Using it
Add this endpoint as a custom connector in ChatGPT or Claude — the loop closes on your desktop.
Describe it
Your AI writes the .workflow.md.
Save it locally
Into an agent-exposed folder.
Validate
Parsed on your device.
Run — with your OK
Approval dialog, then real execution.
Iterate
Errors say exactly what failed.
Runs ask on-screen first; .workflow.md can’t be written through the connector.
Node types
type: every node type reads the same way —
Built-in — work on any item, no service needed
Per service — family.service.verb
Every node is a YAML-like list item, every edge a `a -> b` line. Diffs, reviews, and merges work like any code file.
credentials: points at @auth / @integration names — real tokens resolve from the Vault at runtime, never from the .md.
Label edges for filter [true]/[false] and switch branches, loop with loop.forEach, and route failures with [on_error].