Create Accountor Login
Docs

Simple Automations

Part of the MountDev Ops Workflows documentation. Updated November 17, 2026

MountDev Ops Workflows documentation | Updated November 17, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 5,581 automated checks before it ships, and every screen change is walked through before release.

Where They Are

Simple Automations is a page in the Workflows menu, beside Workflows, Run History, Approvals, and Templates. An automation does something on its own when a record changes: when this happens, only if these are true, then do that. Everything your account does by itself is now in Workflows: use a workflow for work that runs on a schedule, waits, repeats, or stops for an approval, and a simple automation for a quick rule on one change.

Whoever has the permission Add, change, turn on, run, and stop workflows manages them (owners and admins have it to start; set it in Staff, Permissions). The page uses the actions workflows.automations.list, workflows.automations.save, workflows.automations.turn_on, workflows.automations.turn_off, workflows.automations.delete, and workflows.automations.runs. Nothing was lost in the move: every automation, its runs, and whether it is on are as they were. The old address (Settings, Connections, Automations) opens this page.

If your company has not added Workflows, Automations stays in Settings, in the Connections menu, on the Automations part, with the actions core.automations.list, core.automations.save, core.automations.turn_on, core.automations.turn_off, core.automations.delete, and core.automations.runs. They do the same things.

Writing an Automation

Add an Automation (action workflows.automations.save):

  • When: any event: a record added, changed, or deleted in any module, or an app's own event, such as a ticket opening or a form being sent.
  • Only if (optional, up to 10, all must be true): a field of the record and a comparison: is, is not, contains, does not contain, is empty, is not empty, is more than, is less than, changed, or changed to. Text comparisons ignore capital letters. More and less compare numbers, or dates written like 2026-10-07.
  • Then (1 to 10 steps, in order):
    • Change a field of the record.
    • Add a record to any module, with values for its fields.
    • Give the record to a person (its owner).
    • Add a note to a record that takes notes, such as an internal note on a Helpdesk ticket, or a note on a Projects project or task.
    • Notify people by email: owners and admins, the record's owner, or one person in the workspace. Notices go only to people in your workspace, say which automation sent them and why, and link to the record.
    • Send a webhook: the event, to one of your webhooks, whatever events that webhook lists itself.
    • Call a connected service: a POST to one of your API connections, at the path you give, with its saved key and the body you write. A body that starts with { or [ is sent as JSON.
    • Steps your apps add, shown only when that app is added:
      • Send a contract for signature (Contracts): starts a contract from the template you choose for the deal or contact the automation started from, and sends it for signature, the same as selecting Send for Signature. For example: when a deal changes to Won, send the service agreement.

In values, messages, and bodies, {{field}} puts in a field of the record by its key (such as {{name}} or {{email}}), {{id}} its number, {{module}} its module, and {{event}} the event. In a JSON body each value is written safely as JSON text.

A new automation is saved turned off, so you can look it over. Turn On (action workflows.automations.turn_on) checks it against your setup again; Turn Off (action workflows.automations.turn_off) stops it. Delete (action core.automations.delete) removes it; what it already did stays.

How Automations Run

  • An automation runs right after the change that sets it off, as "the automation", with the same record checks as everyone. Its changes are marked Automation in the record's history.
  • Its steps go all or nothing: if any step fails, nothing it changed is kept, and the run shows which step failed and why. A failed run is also written in the Activity Log.
  • Notices, webhooks, and service calls are queued and sent within moments, then tried again if they fail, like any webhook delivery.
  • Changes an automation makes never set off automations, so automations cannot set each other off in a loop. They do reach your webhooks.
  • Runs (action workflows.automations.runs) shows the newest 50 runs, each step's result, and any failure. The list shows how many runs each automation has had, how many failed, and the last failure.

AI Agents

An AI agent you connect (AI Agents) can read your automations and their runs, draft new ones, and turn them off, if you may manage workflows. Anything it saves is always turned off and marked Drafted by an AI agent, and an agent's change to an automation that is on turns it off. Only a person can turn an automation on.

Ask Us Anything

We’d love to hear from you!