Detect new tickets
The workflow checks Zendesk every 3 minutes for newly created tickets and retrieves each requester's profile, including their email address.
LIVE WEBINAR · 18 NOV: Make your SAP Business One ready for Black Friday — live demo 18 November. Save my seat
About this template
Support agents answering order, delivery and billing questions usually have to search ERPNext before they can reply. This template checks Zendesk every 3 minutes for new tickets, matches the requester's email to an ERPNext customer, pulls their 5 latest Sales Orders, 5 latest Delivery Notes and up to 20 unpaid invoices, and posts a three-line OpenAI summary as an internal note.
Key benefits
Inside the flow
Every 3 minutes, the workflow takes each new Zendesk ticket, finds the ERPNext customer with the requester's email and pulls their recent orders, shipments and unpaid invoices. OpenAI condenses this into three lines that are posted as an internal note on the ticket.
The workflow checks Zendesk every 3 minutes for newly created tickets and retrieves each requester's profile, including their email address.
It finds the ERPNext Customer whose email matches the requester, which links the ticket to the customer's account.
It retrieves the customer's 5 most recent submitted Sales Orders with status, delivery progress and delivery date. It also retrieves the 5 most recent submitted Delivery Notes with shipping date, tracking number and transporter where recorded.
It retrieves up to 20 submitted Sales Invoices with an outstanding balance, including amounts and due dates. Results from every lookup are grouped by ticket.
OpenAI condenses the data into three lines: orders (flagging any past their delivery date), the latest shipment, and the total overdue amount with the oldest overdue invoice. If no customer matches, it says so.
The snapshot is added to the Zendesk ticket as an internal note for agents, not as a public reply.
Order, delivery and billing context on every ticket, without opening ERPNext
01
Agents see orders, shipments and unpaid invoices before writing their first reply.
02
Routine questions about orders, deliveries and balances are answered without searching another system.
03
Late orders and overdue balances are flagged up front, so delivery commitments and goodwill offers are made with the full picture.
04
Results are kept separate for each ticket, so busy periods with many new tickets never mix up customer data.
05
Account and payment details are posted only as internal notes, not in public replies to the customer.
01
Agents see orders, shipments and unpaid invoices before writing their first reply.
02
Routine questions about orders, deliveries and balances are answered without searching another system.
03
Late orders and overdue balances are flagged up front, so delivery commitments and goodwill offers are made with the full picture.
04
Results are kept separate for each ticket, so busy periods with many new tickets never mix up customer data.
05
Account and payment details are posted only as internal notes, not in public replies to the customer.
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.