MitDesk docs
Automations

Automations worth building

6 min read Odoo 20.0

This page shows real flows that ship with MitDesk, either as templates or as demo data. For each one you see what starts it, what it does, and what stops for a person. Use them as a start and change them to fit your company.

Who this is for: administrators and managers who plan automations.

You need: Edition: Pro and above (module minddesk_flow). See Editions. To learn the steps and checks, read Automations you can read.

The Automations list with the shipped example flows, their trigger, state and run-as user

The 12 templates

An empty draft offers these templates for its record type. Applying one fills the draft with steps. You still check it, test it and publish it.

Template Record type What it does
Welcome a new contact Contact When a contact with an e-mail address is created, plans a welcome call.
Check new contact details Contact When a contact is created without an e-mail address or phone number, plans a task to complete them.
Follow up with a new customer Contact When a contact becomes a customer, plans a follow-up.
Weekly customer portfolio review Contact Once a week, plans a review on every customer.
Overdue invoice reminder Invoice Every day, plans a payment follow-up on open customer invoices.
Chase a stale quotation Sales order Every week, plans a follow-up on quotations that were sent and not answered.
Triage a new lead Lead Raises the priority of a new lead and plans the next task.
Weekly pipeline digest Lead Once a week, plans a review on every open opportunity with high priority.
Transfer backlog alert Transfer Every day, plans a task on transfers that wait for stock.
Purchase order approval follow-up Purchase order When an order waits for approval, plans a review.
Escalate a blocked project task Task When a task is set to Changes Requested, plans a task to remove the blocker.
Prepare for an upcoming meeting Calendar event One day before the event, plans a preparation task.

The customer templates use the field customer_rank, so they only appear where Accounting is installed. A template is hidden when the record type is missing in your database.

All templates use Create activity (or Set field) steps. These steps change data, so by default they ask a person. See "What stops for a person" below.

Case 1: chase open invoices

Start from Overdue invoice reminder on invoices.

  • Trigger. Every day, on invoices that are customer invoices and not fully paid. The filter is [('move_type', '=', 'out_invoice'), ('payment_state', 'in', ('not_paid', 'partial'))].
  • Condition "Has a due date". The flow goes on only when the invoice has a due date.
  • Step "Chase the payment". Creates the activity "Follow up on this open invoice" on the invoice.
  • What stops for a person. Creating an activity is a write, so it asks until a MitDesk Administrator adds an autonomy rule for it. See Dry runs and grants.
  • Your next step. Tighten the due-date filter, for example only invoices that are already late.

The same job can also be done by a digital employee.

Case 2: leads nobody has picked up

Start from Triage a new lead on leads.

  • Trigger. On creation of a lead.
  • Condition "Nobody assigned yet". [('user_id', '=', False)].
  • Branch "Has an email address?". Checks [('email_from', '!=', False)].
  • Yes: Set field "Raise the priority" sets priority to 1, then Create activity "Qualify the lead".
  • No: Create activity "Find contact details", because a lead you cannot reach needs research first.
  • What stops for a person. The Set field step writes to the lead, and so does each activity. All of them ask by default.
  • What the test shows. Pick a real lead without an owner. The report shows which path it takes and whether each step would run, ask or be refused.

Case 3: quotations that went quiet

Start from Chase a stale quotation on sales orders.

  • Trigger. Every week, on orders with the state "sent": [('state', '=', 'sent')].
  • Step "Chase the quotation". Creates the activity "Follow up on this quotation".
  • Why it is simple. It has no condition and no branch. The filter on the trigger already selects the orders.

See also Case: quote follow-up for a digital employee that does the same work.

Case 4: a meeting tomorrow

Start from Prepare for an upcoming meeting on calendar events.

  • Trigger. On a date. The date field is start, with an offset of minus one day, at 08:00 in the time zone of the flow.
  • Step. Creates the activity "Prepare for this meeting".
  • Each event runs at most once a day.

More examples in the demo data

The demo database contains 12 example flows. They all run as the demo user. Three of them are live, the others are drafts.

Flow Trigger What it does State
Failed jobs · Mitchell follows every one Every morning Finds jobs that failed and adds the demo administrator as follower. Live
VIP customers · Mitchell follows their records Every week For contacts with the tag VIP, adds the demo administrator as follower. Live
Financial approvals · morning watch Every morning For approvals that wait and are financial, adds the demo administrator as follower. Live
New customer · welcome follow-up On creation or update of a contact Checks that the contact is a company. A branch tests for an e-mail address, and the yes and no paths each create an activity (Schedule welcome call, Ask for an e-mail). Draft
Autopilot · daily customer watch (budget-capped) Every day Runs the read-only tool search_records. It has a cost limit and one autonomy rule. Draft
AR overdue-invoice review Every week Writes a review note on company contacts. It carries a rule that cannot work, to show how a blocked rule looks. Draft
Quarterly key-account check-in Every quarter An agent writes a summary of the account, an Approval asks "Escalate to account manager?", and then a follower is added. The approval ends after 2880 minutes (48 hours). Draft
Key-account contact refresh (loop demo) Every month A Loop over the contacts of a company, at most 10, plans an activity on each. Draft
Rejected request · explain it to the requester On update of an approval (field State) If the approval was rejected, an agent explains why, and an activity tells the requester. Draft
Sales · quiet prospect nudge Every week For companies with the tag Prospects, writes a note on the contact. Draft
Purchasing · supplier contact details Every month For vendors without e-mail, writes a note for the buyer. Draft
Support · customer reachability check Every two weeks For companies without a phone number, writes a note on the account. Draft

The flows that use an agent stay as drafts because they need an AI model to run.

One flow run: the flow, the record, the step count and the path timeline

What stops for a person

Every step that changes data goes through the consent gate:

  • Create activity and Set field ask by default. An administrator can let them run alone with an autonomy rule. See Dry runs and grants.
  • Send e-mail and Add followers use a general method call, which MitDesk never lets run alone. They ask a person each time.
  • A Server action step always asks, for the same reason.
  • Changes to financial targets and to MitDesk's own control records always ask. No autonomy rule can change this.

An approval waits in Decisions. When someone decides, the run continues. See Decisions: approving and answering.

An approval that a flow run waits for: the exact call, the preview of the record and who may approve