Update Stripe customer details from support tickets
When a customer shares a billing detail correction with support, tell Notis how to update their Stripe record and report the result.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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 updates buried in tickets are easy to miss when billing records live in a separate system.
- Reduce missed billing detail corrections
- Keep support context close to the resulting update
- Review run reports in your chosen channel
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Stripe once in the Notis portal.
- 2Create an automation with one instruction describing which corrections qualify and how Notis should update the Stripe customer.
- 3Pick the New Zendesk Ticket trigger for the view handling account changes.
- 4Choose where run reports go and test with one real correction ticket.
Questions about this workflow
Can the automation change any Stripe customer field?
The action updates only details provided. State in the prompt which available customer details to update and how to handle ambiguity.
How does it identify the right Stripe customer?
Your prompt should tell Notis how to identify the customer from available ticket details. Confirm the match with a real example before use.
What happens if the ticket lacks enough information?
Instruct Notis to report the missing details for follow-up rather than guess.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Stripe. A trigger fires from one place; an action lands in another.
Zendesk 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.
New User Created
Triggered when a new user is created in Zendesk.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
Zendesk 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.