Make subscription deletions easier to review
Get a structured look at the details Stripe provides when a subscription is deleted, so follow-up starts with context.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Why this helps
A cancellation can be easy to notice and hard to investigate later when its details are scattered across notifications.
- Collects available deletion event details in one report
- Makes later review easier to start
- Surfaces missing context rather than guessing at a cancellation reason
Setup
Build it in a few focused steps.
- 1Connect Stripe and Codeinterpreter once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe in one instruction how to summarize the deleted subscription event data in Python and note missing context.
- 4Select the Stripe Subscription Deleted trigger and choose where run reports go.
- 5Test with one real subscription deletion event.
Questions about this workflow
Will it tell me why a customer cancelled?
Only if the event or data you provide includes a reason. Otherwise, the report can flag that the reason is missing.
Can it compare this cancellation with past churn?
That comparison needs historical subscription data or a baseline supplied to the analysis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Codeinterpreter. A trigger fires from one place; an action lands in another.
Stripe triggers
Codeinterpreter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sandbox
Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Run Terminal Command
Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Codeinterpreter, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Codeinterpreter.