Keep performance incidents with the customer record
Put the test result and customer context together so follow-up starts with the right details in view.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Performance incident details can get separated from the customer record, leaving follow-up dependent on someone remembering to copy them across.
- Keep the incident reference attached to the correct customer.
- Reduce manual copying between test results and billing records.
- Make customer follow-up easier to pick up later.
Setup
Build it in a few focused steps.
- 1Connect Blazemeter and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, ask Notis to summarize the incident from the webhook and update the specified customer's Stripe metadata with the reference and concise summary.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real incident example with its Stripe customer ID and verify the customer update.
Questions about this workflow
Does Blazemeter provide an event trigger for this workflow?
No Blazemeter trigger events are listed here. A Notis webhook starts the automation when it receives an HTTP request.
What information must the webhook include?
Include the Stripe customer ID and a Blazemeter test or result reference that Notis can use to identify and summarize the incident.
Will the automation overwrite other customer details?
It should update only the incident metadata requested in the instruction. Review the test run report to confirm the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blazemeter to Stripe. A trigger fires from one place; an action lands in another.
Blazemeter 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.
Blazemeter 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.