Create Accountor Login
Docs

Client Actions

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

MountDev Ops Subscriptions 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.

What They Are

A Client Action is one thing you let your clients start from their own account, such as creating a site, booking an extra visit, requesting a tax document, or adding a Microsoft 365 user. Each one runs one of your own workflows, with your own connections and keys. You choose the words, what the client fills in, what it costs, who on the client's side may start it, and whether your team says yes first.

Nothing here is made for one kind of business. Any account describes its own actions the same way, and its own AI agent can help.

This page covers setting actions up and sending them. Clients starting them, the price they confirm, and the requests they send are (Planned) and come in later updates, so today a client only sees them listed, and no client starts one.

On the Screen

Client Actions is in the Subscriptions menu, after Services You Sell and just before Settings. It lists your actions under the service each one belongs to, with its cost in words, whether your team says yes first, any flag, and whether it is On, Off, or a Draft. Add a Client Action opens a page (not a pop up, so Save stays in reach) with five parts:

  1. Pick a Workflow. Any workflow you built. The page lists the steps of it that are flagged.
  2. Label and Words. The service it belongs to, its label, one plain sentence for the client, and what it works on: the account, or one thing you name (a Site, a Visit), in the singular and the plural.
  3. What the Client Fills In. Up to 12 inputs, each text, a number, yes or no, or a choice, required or not. An input can never be private: what a client types is sent to you as written, so never ask a client for a password or a key.
  4. Cost and Limits. Included in the plan, included up to a limit and then a Monthly Change, a One-Time Charge, or not allowed, a Monthly Change, or a One-Time Charge. A price comes from one of your products, so it has one source. A limit is a number each month or while the plan lasts. An action can Give Back the count of another (Delete a Site gives back one Create a Site), and can End the Monthly Charge another added.
  5. Who and When. Who on the client's side may start it (Owners Only, Owners and Admins, or Anyone Who Holds the Permission), whether it runs after the client confirms or waits for your team's yes, which results the client is shown when it is done, and the sentence the client sees if it fails.

See What a Client Sees saves the draft and shows the confirm pop up a client will get for its kind, with what the client is sent and the flag. Save Draft, Turn On or Turn Off, and Remove are on the same page.

Draft, on, and Off

A new action is a Draft. A Draft or Off action is offered to no one. Saving never turns an action on.

Turn On is an owner or admin who manages client actions saying yes to exactly what a card shows: the risk first, the cost, who may start it, whether your team says yes first, and every flagged step of its workflow. The yes covers that version. Any change to the action, or to its workflow's steps, turns an On action back into a Draft and cancels the yes.

Flags and the Standing Yes

An action's flag is the strictest of the flag you set and the flags of the steps in its workflow. It can never be lower than the workflow's.

  • Spends Money and Deletes Something steps normally stop for a person every run. For a client action that runs after the client confirms, your yes when you turn it on is a standing yes for those steps, for exactly this action and this version of its workflow, named with your name and the day. It lets the steps run each time a client confirms the cost, with no one on your team. Change either one and the yes is cancelled and the action is a Draft again.
  • Emails a Client is never covered. An action whose workflow has such a step always waits for your team's yes first, and that cannot be changed.
  • Your AI agent can keep or raise a flag, never lower it. A person lowers one only by giving a reason, which is kept.

For Your AI Agent (Through the MCP)

Each tool is its own permission and level. Every save is a Draft, and nothing here starts a request for a client, approves one, or reads a client's account.

ToolActionPermissionLevelWhat it does
client_actions_listsubscriptions.client_actions.listsubscriptions.client_actions_listReadYour actions with state, cost, who may start each, and the flag, and the services, products, and workflows to choose from
client_action_savesubscriptions.client_actions.savesubscriptions.client_action_saveWriteAdd or change one action, always a Draft. A change to an On action returns it to a Draft. The flag can only be kept or raised
client_action_checksubscriptions.client_actions.checksubscriptions.client_action_checkReadThe words a client would see for one action, what it asks for, and the flag. A price shows only to a person who may see prices
client_action_enablesubscriptions.client_actions.enablesubscriptions.client_action_enableWriteTurn off at once, or ask to turn on, which waits for an owner or admin to say yes
client_action_removesubscriptions.client_actions.removesubscriptions.client_action_removeDeleteAsk to remove an action, which waits for an owner or admin to say yes

An API key can do neither of the last two: turning on and removing need a person's yes.

Sending Actions to Your Clients

Send to Clients on Services You Sell (action subscriptions.services_catalog.publish, people only) now also sends each client the actions of the services that client has. Only an action that is On, not removed, and still covered is sent: a step that spends money or deletes something needs your standing yes to match the workflow as it is now, so a workflow changed after your yes is not offered until you turn the action on again.

Each action is sent as words and whole cents: its label and sentence, what the client fills in, who may start it, its cost kind and the price of the product it names, its limit, whether your team says yes first, and its flag. Each carries a version, the fingerprint of exactly those terms, so a request made on terms that have since changed can be told so and asked again. Nothing of your workflow, your products, your steps, or your keys goes with it, and each client gets only the actions of its own services.

A client sees them read only on its service page, under What Your Provider Offers. Clients cannot start them yet (Planned), so nothing runs and nothing is charged. A client whose list would be too large for one message is skipped and counted (too_large in the answer): turn some actions off, or remove some, and send again. The client keeps the list it had.

Who Can Use It

Owners and admins (permission subscriptions.client_actions_manage, Set up the actions your clients can start, and say yes to turning one on). An owner can give it to anyone through a role or permission group.

Removing and Exporting

Remove keeps the action, turns it off, and clients stop being offered it. Nothing is ever deleted. Export Everything includes a Client Actions sheet with every action, removed ones included.

Ask Us Anything

We’d love to hear from you!