Update Stripe customer details from Byteforms forms
Let customers submit account detail changes once, then keep their Stripe record 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
Customer detail changes can sit in a form response while Stripe continues to hold outdated information.
- Reduce repeated edits across customer intake and Stripe.
- Keep changes tied to the correct customer record.
- Use reports to identify submissions that lack a reliable customer match.
Setup
Build it in a few focused steps.
- 1Connect Byteforms and Stripe once in the Notis portal.
- 2Create an automation in Automations, or tell Notis the outcome in plain language from any channel.
- 3In one instruction, ask Notis to find the matching Stripe customer using a reliable identifier in the submission, then update only the supplied customer details.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real customer update and verify the intended Stripe record changed.
Questions about this workflow
How should the form identify the Stripe customer?
Include a reliable identifier such as the Stripe customer ID or an email address that can be matched unambiguously.
Will blank form fields overwrite existing values?
Ask Notis to update only details explicitly supplied in the submission. The Stripe action updates provided details while unspecified fields remain unchanged.
Can this change subscriptions too?
No. This workflow updates customer details. Subscription changes require a separate supported action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Byteforms to Stripe. A trigger fires from one place; an action lands in another.
Byteforms 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.
Byteforms 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.