Bring Baserow table structure into subscription closeout
When a subscription ends, a table inventory can help you orient the account closeout work that follows.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
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.
Why this helps
Subscription endings can be overlooked when closeout work requires finding the right records and process across different tools.
- Retrieve tables from a specified Baserow database when a subscription is deleted.
- Make account closeout easier to begin with database structure in view.
- Use the event as a review prompt; the action does not update subscription records.
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 list tables in the Baserow database you specify when a Stripe subscription is deleted.
- 4Pick the Subscription Deleted trigger and choose where run reports go.
- 5Test with one real example and confirm the report helps with closeout review.
Questions about this workflow
Does this cancel or change anything in Baserow?
No. It retrieves table metadata. Stripe supplies the subscription deletion event.
Can Notis identify the exact customer tables automatically?
The action lists tables in a specified database. Any customer or account context must be available in the event or supplied in the prompt.
What starts the automation?
A Stripe Subscription Deleted event.
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.