Run on a schedule
The workflow runs every 4 hours, India Standard Time.
LIVE WEBINAR · 18 NOV: Make your SAP Business One ready for Black Friday — live demo 18 November. Save my seat
Check ERPNext every 4 hours for Sales Orders past their delivery date and open one high priority Zendesk ticket per late order, with order details in an internal note
Apps used in this template
About this template
Late deliveries usually surface only when the customer complains, because nobody watches ERPNext delivery dates around the clock. This template checks ERPNext every 4 hours for submitted Sales Orders past their delivery date that are not fully delivered, skips orders that already have an unsolved Zendesk ticket, and opens one high priority ticket per late order for the customer.
Key benefits
Inside the flow
Every 4 hours, the workflow finds submitted ERPNext Sales Orders whose delivery date has passed and that are not fully delivered, closed, on hold or completed. For each one without an unsolved Zendesk ticket, it creates a high priority ticket for the customer with an internal note for the agent.
The workflow runs every 4 hours, India Standard Time.
It retrieves submitted ERPNext Sales Orders that are not fully delivered and not closed, on hold or completed, then keeps only those whose delivery date has passed. Each order gets a tracking reference based on its order number.
It searches Zendesk for an unsolved ticket already linked to the order. If one exists, the order is skipped.
For orders without a ticket, it reads the customer's name and email address from the ERPNext Customer record.
It creates a high priority Zendesk ticket for the customer, tagged with the order and marked as a late order.
An internal note gives the order number, original delivery date, delivery progress and order value, and asks the agent to confirm a new date and update the customer.
Late orders reach support before the customer has to ask
01
Support contacts customers about delays before they chase, turning a likely complaint into a service moment.
02
Late orders reach the support queue within hours of missing their delivery date, without anyone monitoring ERPNext manually.
03
Duplicate checks keep a single open ticket per order, even when it stays late across several runs.
04
Agents get the order details, delivery progress and value in the ticket, so they can go straight to confirming a new date.
05
The first note is internal, so agents decide exactly what the customer is told and when.
01
Support contacts customers about delays before they chase, turning a likely complaint into a service moment.
02
Late orders reach the support queue within hours of missing their delivery date, without anyone monitoring ERPNext manually.
03
Duplicate checks keep a single open ticket per order, even when it stays late across several runs.
04
Agents get the order details, delivery progress and value in the ticket, so they can go straight to confirming a new date.
05
The first note is internal, so agents decide exactly what the customer is told and when.
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.