Add rental order context to failed payment follow-up
A failed payment is easier to triage when the related rental order is close at hand.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Get Orders
Tool to list all orders. use when you need to retrieve orders, optionally filtered by search term or paginated.
Why this helps
Payment alerts often arrive without the rental context needed to decide what follow-up is appropriate.
- Pair payment exceptions with possible rental order context.
- Give the team a concise report for human follow-up.
- Avoid taking action on an uncertain order match.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Booqable once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to search Booqable orders using identifiers available in the failed payment and report possible matches for review.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports go.
- 5Test with one real failed payment intent.
Questions about this workflow
Will this retry the payment or contact the customer?
No. The selected Booqable action only retrieves orders. The workflow prepares context for a person to decide what to do next.
Can it always find the matching order?
Only when the failed payment includes details that can be matched to Booqable order data. Notis should report when a match is uncertain.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Booqable. A trigger fires from one place; an action lands in another.
Stripe triggers
Booqable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Customer
Tool to create a new customer. use when onboarding a new client and you have verified their details. example: create 'jane doe' with email jane@doe.com.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Order
Tool to create a new order. use after collecting valid customer id and timing details. example: create an order for customer '297f2584-...' starting at '2018-01-01t09:00:00z'.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create Product Group
Tool to create a new product group in booqable. use when you have defined the group's name and pricing details and want to organize items under a shared group.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Delete Customer
Tool to delete (archive) a customer by id. use after confirming the customer should be hidden from searches.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete Order
Tool to delete (archive) an order by id. use when you need to hide completed or canceled orders from active listings.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Delete Product Group
Tool to delete a product group by id. use when you need to permanently remove a product group from your catalog after confirming its identifier.
Product Created Trigger
Triggered when a product is created in Stripe
Get Customer
Tool to fetch a specific customer by id. use after obtaining a customer identifier to retrieve full customer details.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Get Customers
Tool to retrieve a list of customers. use when you need to paginate through customers.
Connect any two apps with Notis in the middle.
Stripe and Booqable, 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 Booqable.