Add more Product options
under review
T
Thomas Mueller
Please add the following Tasks:
- Cancel Product/Package
- Upgrade Product (Express to Pro)
- Downgrade Product (Pro to Express)
Log In
Nolan Cline
Hey Sumi,
The aim with these suggestions is to enhance the flexibility and comprehensiveness of our automation platform, particularly in the context of low-code/no-code scenarios.
It's true that specific use cases can guide feature development(and Thomas may have some to share), but the broader aim here is to empower our automation system to replicate any user action currently achievable either manually in our platform or programmatically through the API.
Cancel Product/Package: It seems like quite a gap that we allow for forced deactivation, but NOT cancellation, which should likely be the more common event. Partners frequently manage subscription lifecycles programmatically, whether due to customer requests, billing issues, or churn management. Automating cancellations would streamline these common operational tasks.
Check if Product is Active: The use cases you mention are all good ones, but in particular we had a partner wanting to validate the state of which products were active on an account whenever a new activation occurred before proceeding with subsequent workflow steps.
Additionally, while we anticipate in the long run leveraging AI agents to automate complex workflows via our own MCP servers, it's important to recognize the continued need for deterministic workflows. Partners will likely want the option to define absolute, predictable outcomes that eliminate the potential for AI-driven errors, ensuring reliability for critical operations. This is why we should continue to strive for platform action parity for the automations system.
Sumi Uzir
under review
Sumi Uzir
Hello Nolan and Thomas,
Thanks so much for these suggestions — they’re insightful, and I really appreciate you taking the time to share them.
To help us explore these ideas further, would you be open to providing a bit more detail on how you’d like to use each of these in your workflows? Specifically:
What kind of scenarios or business logic would drive the need to cancel, upgrade, or downgrade a product or package through automation?
For the "check if product is active" condition — how would you ideally use that in an automation? (e.g. branching logic, triggering follow-ups, preventing duplicate actions, etc.)
Understanding the intended use cases will help us better evaluate feasibility and potential value for partners.
Looking forward to hearing more — and really appreciate your input!
Best regards,
Sumi
Nolan Cline
I would also suggest 'check if product is active'