Keep Stripe customer details aligned with a Cloudpress client change
When a client change is confirmed, tell Notis which Stripe customer and details to update.
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
A changed client detail in a project record can leave billing records outdated if it is not carried across.
- Apply a confirmed client detail change with one request.
- Specify the exact Stripe customer to update.
- Avoid overwriting fields that were not part of the change.
Setup
Build it in a few focused steps.
- 1Connect Cloudpress and Stripe once in Notis.
- 2Create an automation in Notis and give it a name and prompt.
- 3Tell Notis to update only the Stripe customer details you specify from the Cloudpress client change, including the customer ID.
- 4Choose a webhook trigger and where run reports should go.
- 5Test with one real change and verify the customer record in Stripe.
Questions about this workflow
Will it replace every customer field?
No. The action updates only provided details; unspecified fields remain unchanged.
Does it detect edits in Cloudpress by itself?
No Cloudpress trigger events are listed. Start the workflow with a Notis webhook and provide the confirmed change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudpress to Stripe. A trigger fires from one place; an action lands in another.
Cloudpress 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.
Cloudpress 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.