Keep scheduled performance reviews on customer records
A recurring check can leave a concise pointer to the latest performance review where customer context already lives.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Teams can finish a scheduled performance review but forget to record its latest result alongside the relevant customer.
- Record the latest review date and test reference on the customer record.
- Reduce manual follow-through after recurring performance checks.
- Keep the reviewed cohort and resulting updates visible in run reports.
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, specify the Blazemeter tests and Stripe customer IDs or matching rules to review, then ask Notis to update only the latest review date and result reference.
- 4Choose a recurring schedule trigger and select where run reports should go.
- 5Run one real example and verify the matching customer metadata before relying on the schedule.
Questions about this workflow
Does the schedule discover which Stripe customers correspond to Blazemeter tests?
Only if you provide a reliable customer ID list or matching rule. Notis should not infer customer identity from a test name.
What is recorded on the customer?
The instruction should limit the update to a review date and a result reference, or other specific metadata you choose.
Can I use this to assess whether an SLA was met?
Only if you supply the applicable SLA threshold and the needed test data. The listed apps and actions do not supply an SLA baseline automatically.
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.