Keep supplied lead details aligned with Stripe
When an appropriate profile update arrives, pass its changed details 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
Profile changes can get lost between lead research and billing records when someone has to remember to update both.
- Apply only details supplied in the request.
- Keep customer records current after a verified handoff.
- Reduce manual updates across apps.
Setup
Build it in a few focused steps.
- 1Connect Bread & Butter and Stripe once in the Notis portal.
- 2Create an automation in the portal or tell Notis the profile-update outcome you want.
- 3Ask Notis to identify the existing Stripe customer from supplied identifiers and update only the appropriate provided details.
- 4Pick the notis_webhook trigger and choose where run reports go.
- 5Test with one real profile update and verify the Stripe customer record.
Questions about this workflow
Does this automatically read profile history from Bread & Butter?
No Bread & Butter action or trigger event is listed. The webhook request must include the update information and identifiers needed for the task.
What happens to fields not included in the request?
Stripe's Update Customer action changes only the details provided; unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bread & Butter to Stripe. A trigger fires from one place; an action lands in another.
Bread & Butter 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.
Bread & Butter 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.