Proactive SLA monitoring & ticket escalation with Zendesk, Slack and Google Sheets
Needs changesWhat this workflow does
This workflow has 13 nodes and runs on a schedule (legacy Cron node). Along the way it connects Zendesk, Slack and Google Sheets.
How it runs
Trigger: On a schedule (legacy Cron node).
- Fetch Open Tickets from Zendesk (Zendesk): get many
- Filter: Open Tickets Only (If): checks a condition and branches into true / false
- Calculate SLA Time Remaining (Function): runs custom JavaScript (legacy Function node)
- Notify: No Open Tickets (Slack): uses Slack
- Prepare Escalation Payload (Edit Fields (Set)): sets or maps fields
- Update Zendesk: Warning Priority (Zendesk): update
- If: checks a condition and branches into true / false
- If: checks a condition and branches into true / false
- Prepare Compliance Log (Function): runs custom JavaScript (legacy Function node)
- Update Zendesk: Escalate (90%+) (Zendesk): update
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Cron in Trigger Every Hour: replace with Schedule Trigger.
- Function (legacy) in Calculate SLA Time Remaining, Prepare Compliance Log1: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Trigger Every Hour | Schedule Trigger |
| Function (legacy) Calculate SLA Time Remaining, Prepare Compliance Log1 | Code node, mode 'Run Once for All Items' |
Nodes used (7)
- Cron
n8n-nodes-base.cron - Zendesk
n8n-nodes-base.zendesk - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Function
n8n-nodes-base.function - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets
From the author
Description: Ensure your customer SLAs never slip with this n8n automation template. The workflow runs on a schedule, fetching open tickets from Zendesk, calculating SLA time remaining, and sending proactive alerts to Slack when tickets approach breach…