Update Stripe customer records from Typeform changes
When a customer submits updated details, tell Notis what to change in their Stripe record.
Trigger
New Form Response
Triggers when a respondent completes and submits the form.
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 details arrive through forms but can remain outdated in Stripe until someone remembers to update them.
- Reduce manual customer record maintenance.
- Process customer requested changes closer to submission time.
- Limit updates to the details specified in your instruction.
Setup
Build it in a few focused steps.
- 1Connect Typeform and Stripe once in the Notis portal.
- 2Create an automation and give it a clear name and prompt.
- 3Tell Notis how to identify the existing Stripe customer and update only the submitted details you want changed.
- 4Pick the Typeform New Form Response trigger and choose where run reports should go.
- 5Test with one real form response and check the updated Stripe customer.
Questions about this workflow
How does Notis know which customer to update?
Your instruction must provide a reliable way to identify the existing Stripe customer, such as a customer ID collected in the form or another supported detail.
Will unspecified Stripe customer fields be cleared?
No. The update action changes only the details provided, and unspecified fields remain unchanged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Typeform to Stripe. A trigger fires from one place; an action lands in another.
Typeform 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.
New Form Response
Triggers when a respondent completes and submits the form.
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.
Typeform 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.