Bring Stripe customer context into billing ticket follow-up
Have Notis look up the relevant Stripe customer when a billing ticket arrives, then send the findings to your report channel.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
Support follow-up slows down when you have to search for the right billing record before understanding the request.
- Reduce time spent searching billing records
- Give follow-up a clearer customer context
- Keep lookup results in a report channel
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Stripe once in the Notis portal.
- 2Create an automation with an instruction to identify the Stripe customer from each eligible billing ticket and retrieve its details.
- 3Pick the New Zendesk Ticket trigger for your billing support view.
- 4Choose a report channel, then test with one real ticket and customer.
Questions about this workflow
Does this workflow change Stripe data?
No. It retrieves customer details using the Stripe Retrieve customer action.
What if the customer cannot be identified?
Tell Notis in the prompt to report that it could not confidently identify a Stripe customer, and provide the missing information for follow-up.
Where will retrieved details appear?
They appear in the automation run report channel you select during setup.
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.