Find payment intents that need a Bolna follow-up
Let Notis gather Stripe payment intent records on a schedule and summarize the follow-up decisions you define.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List payment intents
Retrieves a list of stripe paymentintents, optionally filtered and paginated using paymentintent ids as cursors.
Why this helps
Payment records and voice conversations are easy to review separately, leaving follow-ups scattered.
- Bring payment intent records into one review
- Summarize next steps using criteria you provide
- Spot records that need more context before outreach
Setup
Build it in a few focused steps.
- 1Connect Bolna and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the payment review.
- 3In one instruction, define which payment intents to review and what follow-up summary you need.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real example and check that the summary supports your call follow-up.
Questions about this workflow
Can Notis tell why a payment needs follow-up?
Only when the relevant context is available in returned Stripe data or supplied in your instruction. Do not assume Bolna call history is included.
Does this action change payment records?
No. It lists payment intents for review and summarizes them; it does not confirm or update a payment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolna to Stripe. A trigger fires from one place; an action lands in another.
Bolna triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Bolna and Stripe, 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 Stripe.