Find the right Stripe customer from a browser support request
Bring the customer context you need into the support handoff, without opening Stripe to search manually.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
A support request that lacks billing context can send you jumping between browser notes and Stripe.
- Retrieve a customer record using identifiers included in the request.
- Summarize relevant returned details for the support handoff.
- Flag requests that do not include enough information to identify a customer.
Setup
Build it in a few focused steps.
- 1Connect Browserbase and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, ask Notis to identify the Stripe customer from the request and summarize returned details.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real support request and check the report for accuracy.
Questions about this workflow
Does this workflow create or change customer data?
No. It retrieves customer details and reports them for the support handoff.
What if the request does not identify a customer?
Have the instruction ask Notis to report what identifying information is missing rather than guess.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase tool to Stripe. A trigger fires from one place; an action lands in another.
Browserbase tool 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.
Browserbase tool 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.