Miton

For Power users

Automate the boring parts. Keep the judgment calls.

Build visual workflows that trigger on a schedule, on a webhook, or on a chat command. Drag. Connect. Configure. Run. Miton does the rest.

Start building — it’s free See why Miton →

How It Works

1. Open the Workflow Surface

The Workflow Surface is a visual node graph. Triggers on the left. Actions on the right. A canvas in the middle. You connect nodes by dragging lines between them.

2. Pick a trigger

Schedules (“every weekday at 9am”), webhooks (“when a new row arrives in this Google Sheet”), events (“when a new email matches this filter”), or chat commands (“when I type /daily-brief in any chat”). Triggers can be combined.

3. Compose the actions

Each action is a node. The library includes:

Nodes have form-based config. You don’t write code unless you want to (and there’s a “Code” node for when you do).

4. Run and inspect

Every run is logged. Every step has its input, output, duration, and cost. If a step fails, you see why. You can re-run a single step, a branch, or the whole workflow.

What You Can Automate

Daily briefs — Every morning at 7am, Miton pulls your calendar, your unread emails (summarised), the weather, and the top news in your industry, and writes you a 5-minute brief.

Git digests — Every evening, Miton reviews the day’s commits across your repos, summarises the diffs in plain English, and posts to a Slack channel.

Lead enrichment — When a new row hits a Google Sheet, Miton fetches the company info, the LinkedIn profile, the recent news, and writes a one-paragraph summary to a new column.

Inbox triage — Every 15 minutes, Miton reads your unread email, classifies by urgency, drafts replies for the easy ones, and pushes the rest to a triage folder.

Meeting prep — 15 minutes before every meeting, Miton pulls the attendee’s recent LinkedIn posts, the last few emails exchanged, and the open tickets, and gives you a one-page brief.

Receipt extraction — Forward an email receipt to a Miton address. Miton extracts the vendor, the amount, the category, and writes a row to your spreadsheet.

Site monitoring — Every 5 minutes, Miton hits your sites, checks the response time and the content hash, and alerts you on Slack if anything is off.

Social scheduling — Every Monday, Miton drafts 5 LinkedIn posts based on the week’s top industry news. You review, edit, approve. They go out via Buffer.

And anything else you do more than once a week. If it can be described as “when X happens, do Y, then Z”, Miton can automate it.

Why Miton for Power Users

It’s local-first. Your workflows, your data, your runs — they stay on your machine. No “Zapier deleted my workflow” surprises. No vendor lock-in.

It includes the AI. Every workflow can call an AI node. No separate OpenAI subscription. No per-task API billing. The cost is in the model, in the tokens, transparent in the run log.

It composes with the rest of Miton. A workflow can write a Document, update a Canvas, spawn a sub-agent, query the project knowledge index for context, or save to long-term memory. Your automations are not siloed — they participate in the workspace.

It has real debugging. Step-by-step run history. Per-step inputs and outputs. Re-run a single step. Branch-aware error handling. Pause, resume, cancel.

It scales to real complexity. Loops. Conditionals. Sub-workflows. Parallel branches. Error recovery. Rate-limit awareness. The model you don’t outgrow.

It respects your time. A 10-minute daily brief should not take an hour to build. The 10-preset library covers the common cases; you customise from there.

Getting Started

  1. Download Miton
  2. Open the Workflow Surface
  3. Pick a preset (or start blank)
  4. Configure the trigger
  5. Run it

FAQ

Do I need to know how to code? No. The form-based config covers 90% of use cases. The Code node is there for the other 10%.

What integrations are supported? HTTP, SMTP, IMAP, CalDAV, Google Workspace (Sheets, Calendar, Gmail, Drive), Slack, Discord, GitHub, GitLab, Notion, Linear, Trello, RSS, and any REST API via the HTTP node. Custom integrations can be added via the MCP client.

What about long-running workflows? Miton has daemons — background tasks that survive a workflow run. A daily brief daemon runs every day and is reusable across workflows.

Can I trigger a workflow from the chat? Yes. Every workflow can have a chat command trigger (e.g. /daily-brief). You can also call a workflow from a chat turn via the workflow:run tool.

Is it free? Yes. BYOK is always free. The free multi-provider gateway is also free. The free tier includes 10 active workflows, all presets, and all integrations. Pro features (more workflows, longer run history, more cloud model usage) land with v1.0. See miton.dev/pricing for the latest.

Can I import from Zapier / Make / n8n? Not directly. The visual model is different. But the underlying actions are similar; most workflows can be rebuilt in 15 minutes. A migration guide is in the docs.

What about secrets? Miton has a built-in credentials store. API keys, OAuth tokens, database credentials — all stored encrypted, never logged, never returned to the model. Per-integration permission scopes.

Can I run a workflow on a schedule even when Miton is closed? On macOS, yes — via launchd. On Linux, via systemd. On Windows, via Task Scheduler. The daemon is installed automatically when you enable a scheduled workflow.

Pricing

The on-disk source is source-available under the Functional Source License, Version 1.1, with an Apache 2.0 Change Date of 2028-06-12. See LICENSE and docs/LICENSING.md.