Automation — overview
Automate recurring work in Miton: visual workflow builder, local scheduler, webhooks, run inspector, and presets. Overview and links to task guides.
- Product stage
- Development build
- Last reviewed
- 2026-08-27
- Successful result
- The change is visible in the active project.
What this accomplishes
Automate recurring work in Miton: visual workflow builder, local scheduler, webhooks, run inspector, and presets. Overview and links to task guides.
Automation is where you build workflows for work you do more than once a week. You get a visual graph editor, a scheduler that runs on your machine, a loopback webhook receiver, and step-by-step run history with replay.
This page is the overview. Task guides below cover each tool. See also /for-power-users.
Current availability
This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.
Before you start
- A Miton development build, an active project and Automation open.
- A connected model plus permission for every file, network or scheduled action in the workflow.
What Automation does
You can:
- Build workflows in a visual graph, connecting nodes by dragging lines between their handles.
- Schedule runs with cron expressions on your machine — missed runs replay when Miton restarts; no per-trigger cloud fee.
- Receive webhooks on a loopback-only receiver, optionally HMAC-signed, at
127.0.0.1:7733— no need to expose a public endpoint. - Inspect every run at two levels — the run as a whole and each step inside it — and replay a finished run as a new one.
- Dry-run a workflow by substituting fixture values for the nodes you choose, before it runs live.
- Connect to the rest of Miton — dispatch a sub-agent, advance a project Goal, save to memory.
How Automation fits with the other lenses
Miton shares one agent engine across Chat, Writer, Canvas, Code, and Automation:
- Code — code editor, search, sub-agents, per-turn rewind.
- Writer — rich-text editor, citations, export.
- Canvas — visual canvas, forms, local data.
They share memory, model routing, permissions, and undo. A workflow can draft in Writer or react to a form in Canvas.
Node types
A workflow graph is built from: Trigger (manual, scheduled, or webhook), Input, LLM Call, Tool, Branch, Loop, Merge, Code, Subagent, Advance Goal, Write Memory, Output, and the integration nodes — HTTP, RSS, Email, File watcher, Git event, and Approval.
Workflow presets
Eleven built-in presets you can fork: RSS-to-Email Digest, Daily Standup, Social Scheduler, File Backup, Form to Spreadsheet, Scheduled Report, Webhook Receiver, Weekly Summary, Calendar Prep, Content Monitor, and Data Pipeline (ETL).
Pages in this section
- Visual workflow builder — graph, connections, per-node config.
- Local scheduler — cron and missed-run replay.
- Webhook receiver — loopback binding and HMAC auth.
- Run inspector and replay — run and step history, and whole-run replay.
- Dry-run mode — fixture data and safe iteration.
- Workflow presets — the eleven built-in presets.
- Integration nodes — HTTP, RSS, email, file watcher, git event, approval gate.
Shared topics live in the Docs index. Engineering detail lives in ../../architecture/.
What success looks like
Automate recurring work in Miton: visual workflow builder, local scheduler, webhooks, run inspector, and presets. Overview and links to task guides. The result remains attached to the active project when you move to another workspace.
Common failures and recovery
- Inspect the failed run and the exact node output before replaying it.
- Confirm credentials, permissions and test fixtures belong to the active project.
- Use a dry run to isolate a misconfigured node before starting the complete workflow again.