Workflows
Node-based automation in
.workflow.mdfiles — a directed graph of nodes connected by edges, like Zapier or n8n.
Editing
In Arg0 Desktop you can edit the same file two ways — both read and write identical .workflow.md syntax:
- Text - Write the markdown directly
- Canvas - Drag nodes, connect edges, and inspect runs. Node positions are saved into each node's
positionfield
How it works
A .workflow.md file contains a ## @automation block. Each node receives JSON items, processes them, and passes results along its connections to the next nodes.
## @automation daily_summary
enabled: true
timeout: "5m"
context:
channel: "#updates"
workflow:
trigger: trigger
nodes:
- id: trigger
type: trigger.cron
parameters:
schedule: "0 9 * * *"
- id: fetch
type: http.request
parameters:
method: GET
url: "https://api.example.com/metrics"
- id: format
type: transform.template
parameters:
template: "Daily users: {{ $json.total_users }}"
connections:
- trigger -> fetch
- fetch -> format
Node fields
| Field | Required | Description |
|---|---|---|
id | yes | Unique node id within the automation |
type | yes | Node type (see below) |
parameters | no | Node-specific inputs |
credentials | no | Reference to an @auth or @integration |
endpoint | no | For http.request, an ## @endpoint block name |
position | no | Canvas coordinates { x, y } |
on_error | no | Node id to jump to on failure |
Node types
- Triggers —
trigger.manual,trigger.webhook,trigger.cron - Actions —
http.request,action.slack.postMessage,action.notion.createPage, etc. - Data —
filter,switch,transform.set,transform.map,transform.template,transform.format.* - AI —
ai.prompt,agent.instance - Control flow —
delay.wait,delay.until,loop.forEach,loop.splitInBatches,merge.append,merge.combine - Custom code —
code.javascript - Human in the loop —
checkpoint.manualpauses the run for approval
Connections
source -> target with an optional [label] for branches:
connections:
- trigger -> fetch
- filter -> process [true]
- filter -> skip [false]
- switch -> high_priority [high]
- switch -> default_path [default]
Expressions
Use {{ ... }} inside parameters:
{{ $json.title }} # current item's field
{{ fetch.output.total_users }} # another node's output
{{ fetch.count }} # number of items a node produced
{{ $context.channel }} # automation context
{{ $env.API_KEY }} # environment variable
{{ $error.message }} # inside on_error handlers
Credentials
Workflow files never contain secrets. Define how to authenticate with @auth, and tokens are resolved at runtime.
## @auth SlackOAuth
type: oauth2
service: slack
scope: chat:write,channels:read
Reference it from a node — or use @integration to manage multiple accounts:
- id: post
type: http.request
endpoint: SlackSendMessage
credentials: SlackOAuth
Auth types: oauth2, api_key, basic_auth. Tokens can also come from env or the OS keychain.
Endpoints
An ## @endpoint block defines a reusable HTTP call for http.request nodes:
## @endpoint SlackSendMessage
POST https://slack.com/api/chat.postMessage
Auth: SlackOAuth
Body:
- channel: string
- text: string
Error handling
Set on_error on the automation or a single node to route failures to a handler node:
- id: fetch
type: http.request
on_error: notify_failure
Related Documentation
- Triggers - Trigger configuration
- Workflow syntax - Bridge MD reference
- @endpoint - Endpoint blocks
- @auth - Authentication
- @checkpoint - Approval gates