Apply BigML segment decisions to Stripe customer records
Use a segment result to make a specific, reviewable update to a customer record.
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
Segment decisions are easy to lose between analysis and the customer records that billing teams use.
- Carry a segment decision into a specified customer record.
- Limit updates to details included in the instruction.
- Report mismatched IDs or missing values for review.
Setup
Build it in a few focused steps.
- 1Connect BigML and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis which supplied BigML segment result should update which specified Stripe customer details, and to report any uncertain match or missing value without guessing.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real customer and confirm the changed details.
Questions about this workflow
Does this update every customer in a segment?
The workflow should act only on the customer or records explicitly supplied and authorized in the instruction.
Can it overwrite unspecified customer details?
No. The Stripe action updates only the provided details; unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bigml to Stripe. A trigger fires from one place; an action lands in another.
Bigml 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.
Bigml 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.