Update a Stripe payment intent from Zendesk support
Give Notis a clear instruction for supported payment intent changes that begin in a Zendesk payment ticket.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Update Payment Intent
Updates a stripe paymentintent with new values for specified parameters; note that if `currency` is updated, `amount` might also be required, and certain updates (e.g., to `payment method`) can necessitate re-confirmation by the customer.
Why this helps
Payment intent changes can be easy to overlook when the request lives in a support conversation and the record lives elsewhere.
- Reduce repeated entry for payment changes
- Keep the originating request tied to the run report
- Make required customer follow-up easier to spot
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Stripe once in the Notis portal.
- 2Create an automation with a prompt specifying which supported payment intent changes to make and how to handle re-confirmation needs.
- 3Pick the New Zendesk Ticket trigger for the relevant payment support view.
- 4Choose a report channel and test using one real ticket and payment intent.
Questions about this workflow
Can every requested payment intent change be made?
The Stripe action updates specified parameters, but some changes can require customer re-confirmation. Your prompt should account for that and report when follow-up is needed.
What if currency changes?
The action notes that updating currency might also require an amount. Include all required details in the instruction and test with a real example.
Does the ticket trigger make Notis build field mappings?
No. The workflow uses a plain-language prompt to interpret the ticket and perform the instructed action.
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.