Call an Install

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.

Two steps let a workflow call an install, one paired copy of an outside app your account builds or uses. Your workspace signs the call with its own signing key, so the app knows it is really yours. Neither step names any app or vendor; they work with any app whose connection lists its routes.

Call an Install

Calls one listed route on one install (action core.install_call). Choose:

• Install: one of your installs that has proved its address. The step can call only the install's own address, never one you type.
• Route: the name of a route the install's connection lists, such as health.
• Query (optional): up to 20 names with text, number, or yes or no values.
• Body (optional): JSON, for a route that is not GET, up to 20,000 characters.

The step is for routes that can be undone. If the route deletes something or cannot be undone, the step stops and says to use the other one. The app's answer goes on to later steps as status, ok, and its top level ids, numbers, and yes or no values. The run keeps nothing else: no text from the answer, and never the signing key. The version the app reports is kept on the install.

A busy app (408, 429, or a 500 error) is tried again by the workflow's own back off. Any other refusal, such as the app not accepting the signature, fails the step with the status. A test run checks the step and the install and sends nothing.

Call an Install Route That Cannot Be Undone

The same call, only for a route the connection lists as deleting something or not undoable (action core.install_call_irreversible). It always stops for a person: the run waits with a card, and nothing is sent until an owner or an admin presses Confirm. Decline sends nothing. An AI agent, an API key, an automation, and the workflow itself can never confirm. Saving a workflow with this step needs the permission to manage workflows.

Where the Steps Are Listed

Both steps are in the workflow's list of actions (and in workflows_catalog), with the installs you can pick. A step that has an AI agent save it is saved turned off, like every workflow, and only a person turns it on.