Update Stripe customer details from an Apilio request
When an approved request includes verified customer details, Notis can update the specified Stripe customer and report what changed.
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
Small customer detail changes can get lost between an operational request and the billing system.
- Carry an explicit update request into Stripe.
- Reduce manual re-entry of verified contact details.
- Get a report confirming the requested change.
Setup
Build it in a few focused steps.
- 1Connect Apilio and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to update only the verified details included in the request for the specified Stripe customer ID.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one approved real update and verify the resulting customer record.
Questions about this workflow
What should the request include?
Include the Stripe customer ID, the verified details to update, and the instruction for which provided details are authorized to change.
Will omitted customer fields be cleared?
The update action changes only provided details. Tell Notis not to infer or overwrite details that were not included.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apilio to Stripe. A trigger fires from one place; an action lands in another.
Apilio 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.
Apilio 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.