Detect approved returns
The workflow checks Zendesk every 3 minutes for updated tickets. A return counts as approved when an agent adds the approval tag.
LIVE WEBINAR · 18 NOV: Make your SAP Business One ready for Black Friday — live demo 18 November. Save my seat
About this template
Approved returns in Zendesk often wait days while support and finance swap emails to find the invoice, price and quantity. This template checks Zendesk every 3 minutes for tickets with the approval tag, uses OpenAI to extract the invoice number, items and quantities, and creates a draft ERPNext credit note against the original Sales Invoice, capped at the invoiced quantity.
Key benefits
Inside the flow
Every 3 minutes, the workflow picks up Zendesk tickets updated with the approval tag and has OpenAI extract the invoice number, items and quantities. It then builds a draft ERPNext credit note from the matching Sales Invoice lines and replies to the customer with the credit note number.
The workflow checks Zendesk every 3 minutes for updated tickets. A return counts as approved when an agent adds the approval tag.
OpenAI reads the ticket subject, description and tags, confirms the return is approved and not yet processed, and extracts the invoice number, items and quantities. A missing quantity defaults to one unit, and only tickets naming an invoice and at least one item continue.
The workflow looks up the submitted Sales Invoice in ERPNext and retrieves the lines for the requested items, with the invoiced quantity, rate and warehouse.
Each item becomes a return line linked to the invoice line it reverses. Quantities are capped at what was invoiced, and the rate and warehouse come from the original line.
A draft credit note is created in ERPNext against the original Sales Invoice for the same customer, ready for finance to review and submit.
When the credit note exists with its item lines, a public Zendesk reply gives the customer its number. The ticket is then marked as processed so it is never credited twice.
Return credits that match the original sale, without re-keying
01
Customers receive a credit note number within minutes of approval, instead of waiting for support and finance to exchange emails.
02
Every credit uses the price the customer paid, and quantities can never exceed what was invoiced, which prevents over-crediting.
03
Each ticket is marked once its credit note exists, so later updates to the same ticket never create a second credit.
04
Credit notes are drafts for finance to review, and each one references the invoice and invoice line it reverses for a clear audit trail.
05
Invoice numbers, items and quantities move from the customer's message into ERPNext without anyone typing them again.
01
Customers receive a credit note number within minutes of approval, instead of waiting for support and finance to exchange emails.
02
Every credit uses the price the customer paid, and quantities can never exceed what was invoiced, which prevents over-crediting.
03
Each ticket is marked once its credit note exists, so later updates to the same ticket never create a second credit.
04
Credit notes are drafts for finance to review, and each one references the invoice and invoice line it reverses for a clear audit trail.
05
Invoice numbers, items and quantities move from the customer's message into ERPNext without anyone typing them again.
Keep exploring
Every repetitive process between your ERP, CRM, and business apps has a template. Find yours, customize it, and go live today.
Customize the flow
Every trigger and action this template uses is available in the appse ai builder, so the same flow can be rebuilt with your own routing, thresholds and destinations.
Questions & answers
Everything you need to know about this template before you deploy it.
Discover how appse ai has helped businesses automate processes and achieve growth through our users' success stories.
Start free — no credit card, no setup calls required. Use this template as-is or customize every step inside the appse ai no-code builder and go live today.