Apply Basin customer preference updates in Stripe
Keep customer records aligned with their latest submitted preferences by describing exactly what should change.
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 overlooked when customer records live separately from the intake form.
- Process customer detail changes from a dedicated intake.
- Update only the fields the customer supplied.
- Reduce follow-up to correct stale record information.
Setup
Build it in a few focused steps.
- 1Connect Basin and Stripe once in the Notis portal.
- 2Create an automation in Automations, then choose a name and report channel.
- 3Tell Notis to update the specified customer details from eligible preference submissions, using a reliable customer identifier.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real preference submission and an existing Stripe customer.
Questions about this workflow
What counts as a reliable customer identifier?
A Stripe customer ID is direct. If you use another identifier, your instruction must make the matching rule clear and unambiguous.
Will blank form fields erase existing data?
Tell Notis to update only explicitly supplied details. Unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Basin to Stripe. A trigger fires from one place; an action lands in another.
Basin 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.
Basin 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.