Starting a Workflow from a Subscription or an Invoice
Part of the MountDev Ops Workflows documentation. Updated November 20, 2026
MountDev Ops Workflows documentation | Updated November 20, 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 They Are
Four starters in When Something Happens in One of Your Apps, in the group Subscriptions and Invoices. They let a workflow react when something happens on the money side of your own account: a subscription starts, an invoice is paid, an invoice goes past due, or a subscription is canceled. A workflow might create a welcome task, tell your team, turn a service on, or pause one.
They only react. A starter hands the run the event's number, its type, and the record's number, and nothing else. It never charges anyone, never creates or changes a payment, never sends a client an email, and never changes an invoice or a subscription. What a workflow does after the starter is its own steps, and each step has the same checks as always: a step that spends money, deletes, or emails a client stops and waits for a person, however the workflow was written (How Workflows Run).
You need Subscriptions to see the two subscription starters and Invoices to see the two invoice starters. An account without the app does not see them.
The Four Starters
| Starter | Event | It starts |
|---|---|---|
| Subscription Started | billing.subscription.started | When a subscription is added with the status Active, or its status changes to Active (from Paused or from Cancelled). |
| Invoice Paid | billing.invoice.paid | Each time an invoice's status changes to Paid. |
| Invoice Past Due | billing.invoice.past_due | Once, the first day an invoice is found past its due date. |
| Subscription Canceled | billing.subscription.canceled | When a subscription's status changes to Cancelled. |
The labels use US spelling. The stored status choice on a subscription keeps its spelling, Cancelled.
Who or what made the change does not matter. A person, a key, an AI agent, and Cancel Account (when a closed account's service ends and its subscriptions are marked Cancelled) all start the same starters. A change made by a workflow never starts another workflow, so workflows cannot loop. An import starts none of them, so loading old subscriptions or invoices starts nothing.
Subscription Started and Canceled
Subscription Started starts for a new subscription with the status Active, and for one whose status is changed to Active. Editing an Active subscription, such as a note or a date, does not start it. A new subscription added as Paused or Cancelled does not start it either.
Subscription Canceled starts once for each change to Cancelled. Editing a subscription that stays Cancelled does not start it. A subscription that goes back to Active and is canceled again starts it again.
Invoice Paid
It starts once for each change to Paid, whether a card payment, a bank payment, or a person recording a payment by hand paid the invoice. An invoice that is paid, reopened after a returned payment, and paid again starts it twice, and each run has its own event number. A workflow that must act only once checks the invoice's number (use Get a Record on the invoice, or a Wait and a Check Something).
A late fee is an invoice too. Narrow it by Kind (Monthly, Time, Late Fee, or One Time) with Only When (Only Start a Workflow When).
Invoice Past Due
Past due is the day after the due date. Invoices checks once a day, in its own daily run, and writes the first day it finds an invoice open with a balance past its due date as the invoice's Past due on date. That one change starts the starter, once for each invoice:
- The date is written once. It is never cleared and never set a second time, so a payment later does not remove it and the starter does not start again.
- It uses the same meaning of past due as Nonpayment: an open invoice with a balance and a due date, billed here, and never a late fee. An invoice whose bank payment is clearing, that is disputed, whose client is on Hold Collections, whose account is canceled, or whose client is Former gets no date until that ends, and then gets it that day.
- It runs whether Nonpayment is on or off. Turning Nonpayment on or off changes nothing here, and this changes none of Nonpayment's steps, emails, or days (Nonpayment).
- It marks at most 100 invoices in a run, and the rest the next day.
- It writes only that one date. It never sends an email, never makes or changes a payment, and never changes another field.
Invoices that were already past due. The first daily run after this feature ships gives every invoice that is already past due its date quietly, with no event, so turning on a workflow later does not start it for a backlog. Only invoices that become past due after that first run start the starter.
Add One to a Workflow
- Open Workflows, then a workflow's Build tab.
- In What Starts It, choose Add a Starter, then When something happens.
- Choose one of the four in the group Subscriptions and Invoices. The picker shows the group's four starters, each with one sentence, and a Starts about line for the one you chose.
- Add Only When checks if you want to narrow it, then save. A workflow is saved off. Only a person turns it on, and a change an AI agent saves to a workflow that is on turns it off.
Who Sees What
A workflow runs as the person who turned it on, with that person's access at that moment. A run keeps no record values. A step that reads the invoice reads it with that person's field rules, so a person whose role hides the total gets a run that cannot read it.
For AI Agents
There is no new tool. The four events are listed in workflows_catalog with their ids, labels, group, and one sentence, and an agent uses them in workflows_save as a starter. What it saves is off until a person turns it on.
