Create Accountor Login
Docs

Only Start a Workflow When

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 Only When Is

A starter that listens for an event starts a run for every matching event. Only When narrows that. It is a few checks kept on the starter, and an event that does not pass them makes no run at all. Nothing is added to Run History, no step is counted, and no Background work is used. The starter only counts the event as skipped.

A starter with no checks works as it always did, and every workflow saved before Only When keeps starting exactly as before.

Which Starters Have It

Every starter that hands a run named values has Only When:

  • When something happens in one of your apps. The values are the module's fields.
  • When another service sends an event. For GitHub the values are the repository, the branch, and who pushed. For Other Service they are the values you picked on the starter, by the names you gave them.
  • When a client asks for an action. The values are the action, the client's company, the kind of request, and the questions the actions ask the client.

A schedule and a person pressing Run hand over no values, so they have no Only When and refuse one.

The Checks

A starter can have up to 5 checks, and every one must pass. Each check is a value, one of three tests, and what to compare it with:

  • Is compares with one value.
  • Is Not compares with one value and passes when the value is anything else, or empty.
  • Is One Of compares with a list of up to 20 values.

Words are matched without capital letters and without extra spaces. Numbers are matched as numbers, so 1,250 is the same as 1250. A yes or no value is matched with yes or no. What you compare with is typed on the starter or picked from the field's own choices. It is never a value from another step, never a key or a secret, and never a login field.

The picker lists only values the starter really hands over, in plain words. Text, choice, number, yes or no, and date fields are offered. A long text field, a money field, a login field, and a field you cannot see are not.

Under the starter the checks read as one sentence, such as "Starts only when Category is one of Repair or Install, and Priority is not Low."

Who a Filter Reads As

A check on a record's fields reads the record as it is when the event is read, as the person who turned the workflow on, with that person's access at that moment. This is the same rule as the record steps in Working With Your Records in Workflows.

If that person is turned off or removed, or a field you checked becomes hidden from them, the filter cannot be checked, so it fails closed: no run is made. The starter card says why, for example "This filter cannot be checked: the person who turned this workflow on no longer has access." Turn the workflow on again to choose who it runs as.

What a Skipped Event Costs

Nothing. A skipped event uses no Background work. Each starter with checks keeps a count for each day of the events it skipped and the runs it started, and shows them as "Skipped today" and "Started today". The count holds numbers only. It never holds an event, a record, or a value, and it is in Export Everything.

Test with Sample Data

Type made-up values under Only When and press Test the Starter. It says "This would start a run." or "This would be skipped, because Priority is Low." and starts nothing. Test With Sample Data on the workflow, and the workflows.test tool with a sample, say the same for every starter that has checks.

What Only When Never Does

A filter can only remove starts. It never makes a start possible that the starter would not have made without it: a workflow that is off, a change a workflow itself made, and a GitHub push to another branch still start nothing. Everything an AI agent saves is still saved off, and saving a change to the checks of a workflow that is on by an AI agent turns it off. Only a person turns it on, and the Turn On question shows the checks as a sentence.

For Your AI Agent

Through the MCP, workflows_catalog lists, for each starter, the values it can filter on with their kind and choices, and the three tests (under only_when). workflows_save accepts a filter on a starter in triggers, and it is always saved off. workflows_get returns each starter's filter, its sentence, and today's skipped and started counts. workflows_test takes a sample of made-up values and says whether each starter would start. A filter is data: no code, no expression, and no value from another step.

Apps That Declare Values

An app can name what its own events hand over, up to 10 named, typed values on an event, so a filter can check them. Without that, a filter on an event checks the fields of the event's module.

Not Part of Only When

More than, at most, contains, starts with, or between rows, a value from another step, a filter on a step (Check Something does that after the start), a list of the events that were skipped, and re-running them are not part of Only When.

Ask Us Anything

We’d love to hear from you!