Keep Stripe customer contact details in sync with verified updates
Apply a verified customer detail change and receive a report of the exact record updated.
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 contact updates can be missed when account changes arrive outside the billing workflow.
- Start an update from a webhook request.
- Use supplied identifiers and available account context to verify the record.
- Report which customer record was updated.
Setup
Build it in a few focused steps.
- 1Connect ClickHouse and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, ask Notis to verify the customer identity from the request and ClickHouse context, then update only the specified Stripe details.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real example and confirm only intended fields changed.
Questions about this workflow
Will unspecified customer details be overwritten?
The action updates only provided details, so the instruction should limit the update to the requested fields.
What if the customer cannot be verified?
Have Notis stop and report the ambiguity for a person to resolve.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ClickHouse to Stripe. A trigger fires from one place; an action lands in another.
ClickHouse 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.
ClickHouse 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.