MitDesk docs
Modules

MitDesk — Flow Automation

2 min read Odoo 20.0
MitDesk — Flow AutomationDraw an automation on a canvas. It runs through the same gate as a person clicking.

Technical name minddesk_flow.

Edition: Pro and above. See Editions and how the modules fit together.

A flow is a chain of steps that starts on an event or a schedule. You build it in a visual editor, test it with a dry run, and publish it.

The visual flow builder

One flow run and its path

What it adds

  • Thirteen step types. Trigger, condition, branch, switch, loop, action, AI action, agent step, AI condition, assign to employee, subflow, approval and delay.
  • Triggers. Record created, changed, created or changed, or deleted; a repeating schedule; and a date field on a record.
  • Checks before you publish. A flow needs exactly one trigger. Loops, dead ends, unwired switch cases and unreachable steps are refused.
  • A dry run that cannot write. The test walks the real engine inside a savepoint and always rolls it back.
  • Limits per run. Defaults: 200 steps, 60 seconds, 500 records and 200 direct calls. You can also set a cost limit per run and a monthly budget for agent steps.
  • Autonomy rules from the flow. Publishing a flow can create narrow autonomy rules for it. Archiving the flow removes them.
  • Templates. Save a draft as a template. A template holds the steps only, never runs, records or approvals.

Limits that always apply

  • One switch stops everything. Pause / Resume Autopilot stops all unattended runs. Only a MitDesk administrator can use it. Dry runs by people still work.
  • Building and granting are separate. Only a MitDesk administrator can publish a flow that has autonomy rules.
  • Never as an administrator. A flow cannot run as an administrator or an archived account.

Where you find it

  • Automations
  • Configuration ▸ What has run ▸ Flow Runs
  • Configuration ▸ Pause / Resume Autopilot

What to know

  • The trigger "On time" (a date field plus an offset) is not available. It is refused when you publish. Use a schedule or the date trigger instead.
  • A loop body can hold only action and AI action steps. Nested loops, branches, switches, conditions, approvals and agent steps are not allowed inside a loop.

Requirements

Needs minddesk, base_automation.