Keep Stripe customer contact details current from a handoff
If a verified support or deployment handoff includes a corrected customer contact detail, ask Notis to update that specific Stripe record and report the result.
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 customer record corrections often get lost after an incident because someone has to remember to make the same update in Stripe.
- Carry a verified customer correction into Stripe from the handoff.
- Avoid re-entering the same detail after resolving an issue.
- Report which customer record was updated and which cases need review.
Setup
Build it in a few focused steps.
- 1Connect CircleCI and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe which explicitly supplied customer fields may be updated and require review when details are ambiguous.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real, authorized correction and confirm the Stripe record and run report.
Questions about this workflow
Will it change every field in the customer record?
No. Stripe updates only the details provided. The instruction should name which supplied fields are authorized for this workflow.
What if the handoff does not identify the customer?
The automation should flag the missing customer ID or unclear identity for review rather than guessing.
Can it update billing settings too?
Only specify fields supported by the Stripe action and make the intended change explicit in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Circleci to Stripe. A trigger fires from one place; an action lands in another.
Circleci 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.
Circleci 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.