Every delivery checked.
Before it costs you.

Take a ready-made automation or write down how your operation actually runs. It checks deliveries against orders, flags gaps in purchase orders and watches stock, then hands your team the exceptions with a draft next step.

Example instruction: Every morning, pre-check yesterday's deliveries against our open orders, and send me the late or short ones with a draft note to each supplier. ## Flag a delivery when | Situation | What to do | |---|---| | More than 2 days late | Draft a chase note | | Short by 5% or more | Draft a claim note | | Wrong item | Flag it for me | ## Supplier notes - Quote the order number and the expected date. - Keep the tone polite and short. - Never send them — leave them in my drafts.

In your own words.
Built for real work.

One sentence is enough to begin. The same document grows into a full procedure when the job needs it.

  • Plain language

    Write it the way you would brief a colleague. No flowcharts, no code.

  • Rules, tables and exceptions

    Add limits, scoring tables and edge cases as they come up, right in the same document.

  • Judgment, not just steps

    Say what good looks like and when to ask you. It follows the intent, not a rigid path.

Browse advanced workflows

Your files. Your tools.
No new system.

AUTOMATE.md is just another file in your folder. Nothing to migrate, nothing to replace.

  • Starts on its own

    A new email, a schedule, a changed folder or an edited file starts it. No one has to remember.

  • Your apps, connected

    Email, calendars, drives and team apps. Connect only what the job needs.

  • Next to the work

    It sits beside the invoices, CVs and sheets it works on, and reads them like you would.

You stay in charge.
At every step.

It checks and drafts. Your team decides what is ordered and sent.

  • No order placed on its own

    Requisitions and supplier notes wait for a buyer to approve and send.

  • Undo what you don't want

    Every step is recorded, and a file it changed can be put back.

  • Only the systems you connect

    Each automation reaches only the folders and apps you give it.

Ready-made for operations teams. Pick one and run it.

Each one is a plain-language document. Use it as it is, or change the timing, the rules and the tools to match your team.

Delivery pre-check

Every morning, pre-check yesterday's deliveries against our open orders, and send me the late or short ones with a draft note to each supplier.

Every morning

PO intake triage

Check incoming purchase orders for missing header fields and post a short gap list for the buyer to clear.

When a purchase order arrives by email or EDI

Reorder point draft

Every weekday at 7am, compare on-hand stock to reorder points and post one line per item that needs a requisition.

When on-hand stock falls below the reorder point

Freight invoice match

Match incoming carrier invoices to the rate confirmation and the load record, then email the mismatches to the buyer.

When a carrier invoice arrives

ASN discrepancy check

Compare incoming ship notices with the open purchase order and post every mismatched line to the dock.

When an advance ship notice arrives

Work order overdue alert

Find overdue work orders and notify the maintenance lead with the asset and the days overdue.

When a work order passes its due date

Every stage of the work. Every recurring job.

The recurring work operations teams do every week, grouped the way it happens.

  1. 01

    Plan

    Stock levels and replenishment. It breaks when a shortage is discovered on a customer's order.

  2. 02

    Source

    Purchase orders and approvals. It breaks when an order reaches a supplier with a field missing or a duplicate behind it.

  3. 03

    Move

    Receiving goods in. It breaks when counts, condition and paperwork disagree at the dock.

  4. 04

    Track

    Deliveries, service levels and incidents. It breaks when a late shipment is noticed after the customer calls.

  5. 05

    Quality

    Maintenance and quality records. It breaks when planned work waits for a breakdown.

  6. 06

    Improve

    Suppliers, freight and costs. It breaks when invoices are paid without being matched to what was agreed.

Compared with what you use today.

Your ERP's alerts and rules

Flagging thresholds inside the ERP.

They can't read a supplier's email or a scanned delivery note, or draft the next step.

Flowchart automation tools

Moving data between apps at high volume.

Real-world exceptions multiply branches until the flow is harder to follow than the work.

AI chat assistants

Explaining a document when you paste it in.

Deliveries keep arriving while nobody is asking, and the procedure lives in a chat.

AUTOMATE.md

Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.

Around the tools you already run.

Connect only what a job needs. Your inbox, calendar, files and the systems below stay where they are, with nothing to migrate.

Everyday
GmailOutlookGoogle CalendarSlackMicrosoft TeamsGoogle DriveGoogle SheetsExcel
ERP
NetSuiteSAP S/4HANAOdooCin7
WMS
NetstockLogiwaExtensiv
TMS
project44FourKitesDescartes
Inventory
FishbowlUnleashed
Planning
Anaplan
Procurement
Coupa
Fleet
SamsaraMotive
Work management
monday.comAsanaSmartsheet
CMMS
MaintainX
ITSM
ServiceNowFreshservice
Automation
ZapierMake
Quality
MasterControlQualio
Monitoring
GrafanaBetter Stack
BI
Microsoft Power BI
Records
Veeva Vault

What operations teams ask before handing anything over.

Can it cope with messy, inconsistent inputs?
That is what it is for. It reads delivery notes, PDFs, emails and spreadsheets the way a person would, follows the rules you wrote, and asks when something doesn't fit instead of guessing.
Will it place orders or contact suppliers on its own?
Only if you tell it to. The operations automations here draft requisitions and supplier notes for a buyer to send, and you choose which steps wait for your OK.
Do we need to replace our ERP or warehouse system?
No. It works between the systems you already run: the ERP, the carrier portals, the shared inbox and the spreadsheets. Connect only what each job needs.
What happens when something goes wrong?
Every run is recorded: what it read, what it did and what it is waiting on. A failure is reported, never skipped silently.
Where does it run?
On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
How does it connect to our CRM and other tools?
Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
Does it run when my computer is asleep?
It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
How does my team use it?
Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
Do I need anyone technical to set it up?
No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 3

    Try it, then turn it on

    Run it once and check the result. It only runs on its own once you switch it on.

macOS — coming soon