Keep Stripe customer contact details current
Submit a verified change once and let Notis update the corresponding Stripe record.
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 updates arrive in different places, making it easy for Stripe customer records to fall behind.
- Reduce manual edits to customer records.
- Update only details included in the request.
- Receive a report when the customer cannot be identified or updated.
Setup
Build it in a few focused steps.
- 1Connect Cloudflare and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer contact updates.
- 3Tell Notis to find the Stripe customer using the supplied customer ID and update only the contact details included in the request.
- 4Choose the Notis webhook trigger and where run reports should go.
- 5Test with one real customer contact change and review the result.
Questions about this workflow
Does this workflow need a Stripe customer ID?
The instruction should include the customer ID so Notis can target the intended Stripe customer.
Will missing fields be cleared?
The Stripe action updates only the details provided. Unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudflare to Stripe. A trigger fires from one place; an action lands in another.
Cloudflare 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.
Cloudflare 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.