Keep Stripe customer details aligned with approved CloudPDF corrections
When customer information is corrected in your document process, send the approved details to Notis and update the 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
Corrected names, addresses, or contact details can remain inconsistent when updates must be repeated by hand.
- Apply approved customer detail changes to an existing Stripe record.
- Avoid re-entering corrected details in a second system.
- See a run report when the customer reference or requested update needs attention.
Setup
Build it in a few focused steps.
- 1Connect CloudPDF and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer corrections.
- 3Tell Notis to update only the provided details on the Stripe customer identified in the approved correction request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real correction request and inspect the updated Stripe customer.
Questions about this workflow
Will unspecified customer fields be changed?
No. The Stripe action updates only the provided details; unspecified fields remain unchanged.
What should the request include?
Include the existing Stripe customer id and the approved customer details to update. Provide any details that are not available from the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CloudPDF to Stripe. A trigger fires from one place; an action lands in another.
CloudPDF 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.
CloudPDF 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.