Skip to content
Notis

Retrieve a payment intent for a Bolna support call

Give your team a direct view of an identified payment intent when a billing question comes in.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Retrieve payment intent

Retrieves a paymentintent by its id; `client secret` is required if a publishable api key is used.

Why this helps

Payment questions take longer when support has to search for the right transaction during a call.

  • Look up a payment intent by its id
  • Prepare relevant transaction context for a support call
  • Report when account access requires additional credentials

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 lookup.
  • 3In one instruction, tell Notis to retrieve the identified payment intent and summarize details relevant to the caller's question.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real example and confirm the result against the Stripe record.

Questions about this workflow

What information is required to retrieve a payment intent?

The action requires the payment intent id. If a publishable API key is used, a client secret is also required.

Does retrieving the intent change it?

No. This action retrieves details for review.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Confirm payment intent

Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.

ActionInstant

Create Customer

Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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`.

ActionInstant

Create product

Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.

ActionInstant

Create Refund

Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.

ActionInstant

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.