Run your catalog check when a Stripe product is created
Start a consistent catalog review command at product creation, making the next step easier to remember and repeat.
Trigger
Product Created Trigger
Triggered when a product is created 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
Catalog checks are easy to postpone when each new product creates another manual reminder.
- Starts a known terminal routine when a product is created
- Returns command output and error status for review
- Reduces the chance of forgetting a catalog check
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 your catalog check.
- 3Describe in one instruction the command to run and what new product context it should use.
- 4Select the Stripe Product Created trigger and choose a destination for run reports.
- 5Test with one real product creation event.
Questions about this workflow
What should the command check?
Choose a check you already use, such as inspecting a prepared catalog file. Any reference file or expected values must be made available to the sandbox.
Will it change the Stripe product?
The terminal command runs in Codeinterpreter. This action does not edit a Stripe product.
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.