Run your payment failure diagnostic routine
Kick off a consistent diagnostic command when a payment intent fails, with the investigation context ready for review.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
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.
Why this helps
Repeating the same first steps for payment issues takes attention away from fixing the underlying problem.
- Starts a repeatable terminal routine on a failure event
- Keeps investigation steps consistent
- Lets you inspect stdout, stderr, and the command result
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 the diagnostic.
- 3Tell Notis in one instruction which safe diagnostic command to run and what event context to include.
- 4Choose the Stripe Payment Intent Failed trigger and a run report destination.
- 5Test with one real failed payment example.
Questions about this workflow
What command should I run?
Use a command you already trust for diagnostics and describe its purpose in your instruction. The terminal action returns output and an error code.
Will it retry or alter a payment?
This workflow runs a terminal command in Codeinterpreter. It does not itself retry or change a Stripe payment.
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.