Workflows Through Your AI Assistant
Part of the MountDev Ops Workflows documentation. Updated November 6, 2026
MountDev Ops Workflows documentation | Updated November 6, 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 3,243 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.
What Your Assistant Can Do
Your own AI assistant, connected in Settings, Connections, can build and look after your workflows as plain data, the same steps you see on the Workflows screens. It never writes code and it never sends SQL. Each tool below is its own permission, so you choose which ones a connection gets, one at a time, in the connection's permission list.
| Tool | Permission | Level | What it does |
|---|---|---|---|
workflows_list | workflows.list | Read | Lists the workflows with their steps, what starts each one, and whether it is on. It reads them a page at a time. |
workflows_get | workflows.get | Read | Shows one workflow by its number, with what it is estimated to use. |
workflows_catalog | workflows.catalog | Read | Lists the actions a workflow can be built from, what each needs and gives back, which ones need a person, the events that can start one, and how steps and starters are written. |
workflows_save | workflows.save | Write | Adds a workflow, or changes one by its number. |
workflows_test | workflows.test | Read | Tests a saved workflow, or a draft, without running it. |
workflows_enable | workflows.enable | Write | Turns a workflow off now, or asks for it to be turned on. |
workflows_runs | workflows.runs | Read | Shows recent runs and what each step did, as ids, counts, and short plain reasons. |
The actions behind them are workflows.list, workflows.get, workflows.catalog, workflows.save, workflows.test, workflows.enable, and workflows.runs. A connection only gets a tool you ticked for it, and only if the person who made the connection could do that themselves. Owners and admins are the only ones who can give a write permission.
What Stays with You
- Saved off. Everything your assistant saves is off. Saving a change to a workflow that is on turns it off, so a change never goes live by surprise.
- Turning on waits for a yes. When your assistant asks to turn a workflow on, the request waits in the workspace for an owner or admin, with the workflow's name, its version, and its number of steps. Your assistant can check the answer with the approval check tool. If the workflow is changed after the request, the old yes does not turn on the new version.
- Turning off is immediate. Your assistant can switch a workflow off at once and its schedule stops.
- Cards stay yours. A step that spends money, deletes data, or emails a client always stops and waits for a person to press Confirm. Your assistant cannot see, confirm, or decline a card, cannot start a run, and cannot stop one.
- Only what it could do itself. A workflow your assistant saves can only use actions that the person behind the connection could use themselves. The list of actions leaves out the rest.
- No keys. Keys and tokens never go in a workflow. A workflow that has one is refused. Your account's connections supply them when a step runs.
- A record of everything. Every call is in the Activity Log with the connection's name, and every run is kept in your account as before.
Testing a Workflow First
workflows_test goes through a workflow step by step and says what each one would do, without starting a run and without saving anything. It is the same Test Run the builder screen uses. Conditions and waits are described, not followed, and a card is described as one a person would have to answer. An action runs only if its entry in the catalog says it has a test mode, and then it works from a read only view of your data and changes nothing. An action with no test mode is not run at all, and the test says so. A step that spends money, deletes data, or emails a client only ever runs in test mode, so nobody is charged, deleted, or emailed.
Web Service Steps Planned
The step that calls a web service is its own addition to Workflows. When it is added it is an action like any other: it appears in the list of actions with its inputs, your assistant adds it to a workflow as data, and workflows_test checks it the same way, without calling any address. Nothing in these tools is built for one outside service.
Who Can Do What
- Connect an assistant and give it read permissions (owners, admins, and anyone whose role allows connecting an assistant to the workflows they can see).
- Give write permissions (owners, admins, and anyone whose role allows giving a connection write permissions).
- Say yes to turning a workflow on (owners, admins, and anyone whose role allows both giving connection permissions and managing workflows).
- Confirm or decline a card (owners and admins, as before; never an assistant).