Find the relevant Stripe customer from a Bolt IoT alert
If an alert includes a customer email, use it to find the corresponding Stripe record in the same run.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List customers
Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
Why this helps
Finding the customer tied to an operational alert can add another manual search at the wrong moment.
- Search Stripe using an email or other supported filter supplied in the event context.
- Surface matching customer records for follow-up.
- Avoid searching a separate billing dashboard.
Setup
Build it in a few focused steps.
- 1Connect Bolt IoT and Stripe once in Notis.
- 2Create an automation in the portal or tell Notis the outcome in plain language.
- 3Ask Notis to search Stripe customers using the email or identifier included in a Bolt IoT alert webhook and summarize matches.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real alert containing a customer identifier.
Questions about this workflow
What if the webhook contains no customer identifier?
Notis can report that the identifier is missing; provide an identifier or matching rule for a useful lookup.
Does this change customer records?
No. It searches and summarizes customer records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolt iot to Stripe. A trigger fires from one place; an action lands in another.
Bolt iot 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.
Bolt iot 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.