Keep a Stripe customer record current after a web form update
When a customer submits updated details, Notis can carry the relevant changes into their existing 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
Customer information can drift across forms and billing records, making later follow-up harder.
- Reflect verified changes in the existing customer record
- Avoid retyping customer updates into Stripe
- Use only details present in the form submission
Setup
Build it in a few focused steps.
- 1Connect Browserless and Stripe once in the Notis portal.
- 2Create an automation from any channel, or use Automations, New Automation in the portal.
- 3In one instruction, ask Notis to update the identified Stripe customer using only verified form details.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real customer form submission and review the run report.
Questions about this workflow
Does this workflow create a customer if none is found?
No. It is for an existing Stripe customer identified in the submitted details. Define how Notis should handle an unclear or missing customer id.
Will it overwrite unspecified customer fields?
The Stripe action updates only provided details, leaving unspecified fields unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserless to Stripe. A trigger fires from one place; an action lands in another.
Browserless 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.
Browserless 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.