MountDev Ops Workflows
How MountDev Ops Workflows works, page by page. Updated November 5, 2026
MountDev Ops Workflows documentation | Updated November 5, 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 2,744 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
Tested Every Release
All 25 of Workflows's own automated checks run on every update.
What they cover: Roles and permissions
What Workflows Is
Workflows is work your account does by itself. A workflow is a list of steps that starts on a schedule, when something happens in one of your apps, or when you press Run. Each step runs an action, checks a condition, waits, or stops for your OK. Every run is kept, with what each step did, so you can always see what happened and when.
Everything about your workflows lives in your own account: the workflows, what starts them, every run, and the cards waiting for your OK. Nothing is kept anywhere else.
In These Docs
- How Workflows Run: what starts a workflow, the four kinds of step, retries, the cards that wait for you, and the run history.
- Workflows Settings: who can manage workflows and answer cards, and how a workflow is turned on.
Who Can Do What
- Add, change, turn on, run, and stop workflows (owners and admins).
- Confirm or decline the cards a workflow waits for (owners and admins; a card for an owner is for an owner).
- Members cannot see or change workflows. AI agents, API keys, and assistants never save, turn on, run, or confirm one: those stay with people.