Carry verified shopper preferences into Stripe
Keep customer details aligned when shoppers share a preference update that your team has permission to use.
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
Preference updates can be recorded in one customer system while outdated details remain in the billing record.
- Apply only verified preference changes
- Reduce repeated customer detail edits
- Keep a clear report of each update
Setup
Build it in a few focused steps.
- 1Connect Bluebarry and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for preference updates.
- 3In one instruction, tell Notis to require verification and consent, match the Stripe customer by a supplied ID, and update only the supplied details.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Test with one real consented update and review the resulting customer record.
Questions about this workflow
Does this workflow infer consent from profile data?
No. Send a clear consent signal with the webhook input and instruct Notis to skip updates without it.
What happens if the Stripe customer ID is missing?
Have Notis report the case for review rather than guessing which Stripe record to change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bluebarry to Stripe. A trigger fires from one place; an action lands in another.
Bluebarry 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.
Bluebarry 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.