Keep member contact changes in sync with Stripe
When a member's contact details change, pass the approved update to the matching Stripe customer.
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
A member can update their directory profile while billing contact details remain outdated in Stripe.
- Apply supplied contact changes to the identified Stripe customer.
- Reduce mismatches between directory and billing records.
- Keep updates scoped to the fields included in the request.
Setup
Build it in a few focused steps.
- 1Connect Brilliant Directories and Stripe once in Notis.
- 2Create an automation in Notis and name it for Stripe customer updates.
- 3Tell Notis to update only the provided fields for the Stripe customer ID in each member change request.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real member detail change.
Questions about this workflow
Does the workflow find the Stripe customer automatically?
Provide the Stripe customer ID or a reliable lookup instruction in the request.
Will omitted fields be cleared?
No. The action updates only the provided details, leaving unspecified fields unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Brilliant directories to Stripe. A trigger fires from one place; an action lands in another.
Brilliant directories 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.
Brilliant directories 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.