Bring customer context into the incident report
When an alert points to a customer, gather the Stripe record alongside the incident so you can respond with less searching.
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
Responders lose time looking up a customer separately while trying to understand a payment incident.
- Adds customer account details to incident triage
- Reduces separate dashboard searches
- Keeps the customer reference with the run report
Setup
Build it in a few focused steps.
- 1Connect Better Stack and Stripe once in the Notis portal.
- 2Create an automation named Add Stripe customer context to an incident.
- 3Tell Notis: When the webhook includes a Stripe customer ID, retrieve that customer and summarize relevant account details in the run report; note when the ID is missing.
- 4Pick the webhook trigger and choose where run reports go.
- 5Send one real incident webhook with a customer ID to test.
Questions about this workflow
What is required to retrieve a customer?
The webhook request context needs that customer's unique Stripe ID.
Will this workflow edit the customer record?
No. It retrieves existing details and summarizes them in the run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better stack to Stripe. A trigger fires from one place; an action lands in another.
Better stack 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.
Better stack 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.