Revenue operations5 nodes$69 setup
Subscription management assistance
Summarise plan changes, flag failed payments and prepare the human follow-up.
The business problem
Subscription operations generate repetitive admin and failed payments go unnoticed.
Who it is for
SaaS and membership businesses on Stripe.
What the workflow does
▶
Subscription eventtrigger
Payment failed?◇
Payment failed?condition
true → Draft a recovery message · false → Done✦
Draft a recovery messageai
Approve the recovery message☑
Approve the recovery messageapproval
Done■
Doneend
terminalSetup requirements
Requires Stripe access. Refunds and plan changes always require a human.
| Integration | Status | Actions used |
|---|---|---|
| Stripe | Available | Create customer |
Limitations, stated plainly
- Any integration listed as “requires setup” will fail until an adapter is enabled and credentials are stored.
- AI steps without a configured provider produce deterministic simulation output, labelled as such in the run log.
- Steps marked optional record a failure and let the run continue; all other step failures stop the run.
- Approval steps pause the run until an authorised teammate decides.