Keep report client contact details current in Stripe
Make a verified correction once and keep billing contact details current.
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
Contact corrections often arrive in document requests but do not reach the billing record until someone remembers to make a second update.
- Carry verified contact corrections into Stripe promptly.
- Preserve fields the request does not mention.
- Create a clear run report if the customer cannot be identified.
Setup
Build it in a few focused steps.
- 1Connect Carbone and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for billing contact corrections.
- 3Describe in one instruction how to update contact details for the supplied Stripe customer ID.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request that includes a verified customer ID and contact correction.
Questions about this workflow
Does this workflow verify a customer's identity?
It can use the Stripe customer ID supplied in the request, but it does not independently verify identity.
Can it update details not included in the request?
No. The instruction should limit changes to details supplied in the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Carbone to Stripe. A trigger fires from one place; an action lands in another.
Carbone 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.
Carbone 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.