Turn a customer update request into a reviewed change
Keep record maintenance tied to a clear request and a concise report of 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 record updates can linger when customer context and the requested change are in separate places.
- Use the customer ID and requested changes from the incoming request.
- Review the existing record before applying changes.
- Report missing details or conflicting requests for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Census bureau and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer updates.
- 3In one instruction, ask Notis to retrieve the specified Stripe customer, validate the requested change, update only explicitly requested details, and use Census information only if the request calls for it.
- 4Choose a webhook as the trigger and select where run reports should go.
- 5Test with one real example and review the result.
Questions about this workflow
Can Census data automatically change customer details?
No. Census statistics are not customer-specific. Require an explicit update request and a valid Stripe customer ID before changing a record.
What happens if the customer ID is missing?
The automation should report that it cannot identify the customer and request the missing ID instead of guessing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Census bureau to Stripe. A trigger fires from one place; an action lands in another.
Census bureau 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.
Census bureau 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.