Starting a Workflow from a Subscription
Part of the MountDev Ops Subscriptions documentation. Updated November 20, 2026
MountDev Ops Subscriptions 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
Two Workflows starters are about your clients' subscriptions, in the group Subscriptions and Invoices of When Something Happens in One of Your Apps:
- Subscription Started (
billing.subscription.started) starts when a subscription is added with the status Active, or when its status changes to Active, from Paused or from Cancelled. Editing an Active subscription does not start it. - Subscription Canceled (
billing.subscription.canceled) starts once for each change of a subscription's status to Cancelled, whether a person, a key, an AI agent, or Cancel Account made it. Editing a subscription that stays Cancelled does not start it. The stored choice keeps its spelling, Cancelled.
They only react. A starter hands the run the event's number, its type, and the subscription's number, and never changes a subscription, charges anyone, or sends a client an email. An import starts none of them. A workflow is saved off, and only a person turns it on. See Starting a Workflow From a Subscription or an Invoice for the whole page, including the two invoice starters.
