Update Stripe customer details from Apaleo billing changes
Carry a billing contact change through to Stripe without editing the same details twice.
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 details can drift between hotel operations and Stripe when updates are handled in separate steps.
- Reduces repeated edits to customer records.
- Updates only the details included in the request.
- Helps keep billing communication details current.
Setup
Build it in a few focused steps.
- 1Connect Apaleo and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to update the matching Stripe customer using the customer id and only the changed details supplied in the incoming request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real billing contact change and inspect the updated Stripe customer.
Questions about this workflow
What identifies the Stripe customer to update?
Provide the existing Stripe customer id in the request or a reliable way for Notis to resolve it before the update.
Will unspecified customer details be cleared?
No. The action updates only provided details; unspecified fields remain unchanged.
Can this find the Stripe customer from a guest name alone?
A guest name may not uniquely identify a customer. Provide a stable Stripe customer id or enough reliable matching context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apaleo to Stripe. A trigger fires from one place; an action lands in another.
Apaleo 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.
Apaleo 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.