Starting a Workflow When an Action Finishes
Part of the MountDev Ops Workflows documentation. Updated November 19, 2026
MountDev Ops Workflows documentation | Updated November 19, 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 8,865 automated checks before it ships, and every screen change is walked through before release.
What It Is
When an Action Finishes is a starter. It starts a workflow when a Connection Action of your own connections ends. A Connection Action is one call to an outside service that you described once, such as creating a site or booking a visit (Connection Actions). Some of those calls are slow: the service hands back a job and the action keeps asking until the job is done. This starter lets another workflow react when that ends, without a schedule that checks again and again.
What Counts as Finishing
The end of a step that ran a Connection Action, an action named like northwind_hosting.create_site. Built-in actions, Call a Web Service steps, and every other kind of step do not raise it.
A step can end three ways, and the starter picks which ones start it. Pick one or more:
- Job Started. The first call worked and the service handed back a job to wait on. It happens once for each step, and only for an action that has a job wait.
- Done. The step ended well: the call worked, and the job, if it had one, finished.
- Failed. The step ended in failure, once, after its last try. The step's tries and the job's own checks are used first (How Workflows Run).
Done is the start.
Which Action
The starter names a connection (one of your own, or Any Connection) and an action name: one action picked from a list, or a pattern with * standing for any run of letters, digits, and _, such as create_*. The pattern may use lower case letters, digits, _, ., and *, up to 80 characters. A starter may be written before the action exists. The card says "No action matches yet" until one does, and "Matches 1 Action" or "Matches 3 Actions" after.
A starter on a connection that is not in your account is refused.
What the Started Run Gets
What Started It carries these values and nothing else:
connection,action, andoutcome(Job Started, Done, or Failed).runandworkflow: the numbers of the run whose step finished and of its workflow, so a later step can look it up.reason: for Failed, the step's short plain reason, with anything that looks like a key, a token, or an address taken out. Empty otherwise.- The action's own Keep Values by the names it gave them, for Job Started and Done, only the ones the action declared. A value that looks like a key is never kept, so it is never passed on.
Never the action's inputs, never a Private input, and never the answer's text beyond what a Keep Value took. Later steps read these like any value from What Started It.
Only When
The Only When filter works here (Only Start a Workflow When) on the connection, the action, the outcome, and the Keep Values, so one workflow can start only for one region, one plan, or one kind of job.
Exactly Once
A finish starts at most one run for each workflow that listens, however often the engine wakes or a step is tried again after a crash. The run's slot is the finishing run, step, and outcome.
Cost
The starter and the filter are free. The run it starts counts like any run. Every step that spends money, deletes data, or emails a client still stops for a person, and nothing it does is automatic that a workflow could not already do.
How a Run Began
In Run History a started run says how it began, for example "When Create a Site finished", with the connection, the outcome, the run that finished it, a button that opens that run, and the values it was given. The finishing run's step is unchanged and does not show who it started.
Keeping It from Looping
A change a workflow itself made to a record never starts a workflow. This starter is the one narrow exception, because a Connection Action only ever runs inside a workflow. Three rules keep it finite:
- One hop. A run started by this starter does not start any run through it when its own actions finish. The chain is the finishing run, then at most one started run, then it stops. Two workflows that listen to each other's actions start one hop and stop.
- Not its own action. A workflow whose starter names an action it uses itself, or a pattern that matches one, is refused when you save it: "This workflow listens for an action it uses itself."
- A rate guard. At most 100 runs a minute are started this way in one account. Past that, a finish is not turned into a run and the Activity Log says so once for that minute, with counts only. The run that finished is not slowed or failed.
A workflow that is off misses finishes. They are not saved for later.
Same Account Only
The event never leaves your account. An action that finishes in your account never starts a workflow in another account, and another account's actions never start yours.
For Your AI Agent
Through the MCP, workflows_catalog lists this starter (under action_finished): the three outcomes, your connections with their actions and the values each action keeps, and the loop rules. workflows_save accepts { kind: "action_done", connection, name, outcomes, filter } in triggers, and it is always saved off. workflows_get returns the starter, a sentence for it, and how many actions match. workflows_test takes a sample with an outcome and the kept values and says whether a run would start. workflows_enable waits for an owner or admin, and the question says in words what starts it and "This starts by itself when another workflow's step finishes."
Not Part of This
Built-in actions and Call a Web Service steps as a source, an action finishing in another account starting a workflow here, more than one hop, a starter on a whole workflow finishing, running again the finishes missed while a workflow was off, passing on an action's inputs or answer text, and a finish raised by a test run (a test never starts a run).
