Find the right Baserow workspace for failed payment follow-up
A failed payment is easier to handle when you can quickly see which Baserow databases are available for your follow-up process.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
List Databases
This tool retrieves a list of all databases in a specified workspace. as a fundamental operation, it allows users to discover which databases are available in their baserow workspace. this operation is independent and requires only authentication in order to fetch essential metadata for subsequent operations.
Why this helps
Failed payments can be easy to lose track of while switching between Stripe and Baserow to find the right place for follow-up.
- See available databases when a payment intent fails.
- Reduce the time spent searching for a place to handle payment follow-up.
- Keep the event as a prompt to review your process; this action only retrieves database metadata.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Baserow once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3Tell Notis to retrieve the Baserow database list when a Stripe payment intent fails and include it in the run report.
- 4Pick the Payment Intent Failed trigger and choose where run reports go.
- 5Test with one real example and confirm the returned database list is useful.
Questions about this workflow
Does this create a Baserow payment record?
No. The available Baserow action lists databases; it does not create or update records.
What starts this automation?
A Stripe Payment Intent Failed event.
Can Notis choose a database based on payment details?
The action retrieves the available database list. Choosing or updating a specific database record is not supported by the listed action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Baserow. A trigger fires from one place; an action lands in another.
Stripe triggers
Baserow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Databases
This tool retrieves a list of all databases in a specified workspace. as a fundamental operation, it allows users to discover which databases are available in their baserow workspace. this operation is independent and requires only authentication in order to fetch essential metadata for subsequent operations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Tables in Database
This tool lists all tables within a specified baserow database. it allows users to retrieve information about all tables in a database by using the get /api/database/{database id}/tables/ endpoint. the expected output is an array of table objects containing details such as id, name, order, database id, type, and first row header.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
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 Baserow, 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 Baserow.