Workflows

Three ways to create a workflow

The module opens on a welcome with three cards. Pick your path and you land on the matching flow.

Triggers (10)

Each trigger accepts an optional filter (branch, file extension, provider…) that narrows events before firing the workflow.

Action steps (8)

Each action step has its own form in the app and produces a result that later steps can reference.

Control flow

Beyond the flat sequence, workflows support control structures to branch, iterate, parallelise and handle errors.

The engine executes all six step kinds. The visual editor currently exposes: action step, Wait and Conditional (one nesting level). Loop, Parallel and Try/Catch work in the engine but are not in the editor yet.

Bindings between steps

Any form field accepts literals or bindings with the `{{...}}` syntax to reference other workflow variables. If an expression doesn't resolve, it returns an empty string — workflows are tolerant to steps that were skipped by a conditional branch.

Each configuration bottom-sheet includes a visible hint with the syntax so the binding system is discoverable from the UI.

Reliability — retry, timeout and backoff

Every action step has a collapsible Reliability section with five fields. If a step fails, it retries with the chosen wait strategy until attempts are exhausted.

If a step with a timeout sits inside a try / catch block, the catch runs automatically with the error message available as a variable.

Scheduling — interval or cron

Any workflow with a manual trigger can have one or more schedules attached. They survive app shutdown and are auto-rescheduled on launch.

Execution history

Each execution is persisted with the full snapshot of every step's result. It survives crashes and app shutdowns.

• •Newest-first timeline per workflow with status icon and colour
• •Per-run detail: step by step with duration, output rendered in monospace and error message if any
• •Step statuses: SUCCESS (green), FAILURE (red), SKIPPED (grey), TIMED_OUT (orange), RUNNING (blue)
• •Automatic retention: up to 100 runs per workflow + 30-day cap

The "▶ Test now" button in the editor runs the workflow without persisting the run or emitting events — useful to iterate while designing without polluting the history. Side effects (commands, notifications, AI prompts) do execute: it's a real test, not a dry preview.

AI generator

Workflows as AI agent tools

Any workflow you mark as "Available to AI agent" in the editor is automatically exposed as a tool in the AI chat. The agent decides when to call it and passes parameters, which arrive in the workflow as variables (`{{var.<key>}}`).

Only enabled workflows with the option ticked are exposed. The description the model sees is what you write in the "AI tool description" field (or the general description if empty). Agent invocations are persisted in history like any manual run.

Built-in templates (8)

Tap "Activate" on any of them to create an editable copy with a fresh UUID. If you already have an active copy of that template, the button is disabled to avoid duplicates.

You can also install workflows from the Marketplace — they show up as regular copies in "My workflows".

Free vs Pro

Module statistics