Block 1 - Trigger Every Hour
- Type / Role
- n8n-nodes-base.cron - cron
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
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...
n8n-nodes-base.cron, n8n-nodes-base.stickynote, n8n-nodes-base.zendesk, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.function, n8n-nodes-base.set, n8n-nodes-base.googlesheets
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Rahul Joshi.
Original n8n.io sourceEnsure 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 thresholds (75% and 90%). It also updates ticket priority in Zendesk and logs compliance metrics to Google Sheets for reporting. Perfect for support operations, CX teams, and SaaS companies looking to maintain SLA compliance and reduce response delays automatically.
β° Run Every Hour: Automatically triggers every hour to check for SLA-sensitive tickets. π₯ Fetch All Open Zendesk Tickets: Pulls all tickets via the Zendesk API, returning essential fields: ID, status, created_at, sla_due, and priority. π Filter Only βOpenβ Tickets: Excludes closed, on-hold, or pending tickets β monitoring focuses only on actionable cases. β±οΈ Calculate SLA Time Remaining: Computes total SLA duration, remaining minutes, and % of SLA consumed for each ticket. π‘ Warn at 75% Threshold: When 75% of the SLA window has passed, automatically sends a Slack warning to the #general-information channel. π΄ Escalate at 90% Threshold: For tickets nearing breach (β₯90%), the workflow updates Zendesk ticket priority to βHigh,β adds escalation notes, and notifies the support team for immediate action. π Log SLA Compliance in Google Sheets: Each ticketβs SLA metrics (ID, % elapsed, time remaining, timestamp) are appended to a Google Sheet for tracking and reporting. β No-Ticket Confirmation: If no open tickets exist, the workflow posts a ββ No open ticketsβ message to Slack β keeping teams informed of a clear queue.
β±οΈ Automated SLA tracking and escalation π Real-time logging to Google Sheets β‘ Hourly auto-trigger β no manual checks needed π’ Slack alerts at warning and critical thresholds π Dynamic Zendesk ticket updates via API
π¬ Proactively manage customer support SLAs π¨ Automatically escalate critical tickets before breach π Maintain transparent SLA compliance reporting π’ Keep your support team updated in real time
Zendesk API β for ticket retrieval and updates Slack API β for alert notifications Google Sheets β for compliance and reporting logs
β Prevent SLA breaches before they happen β Automate escalation and communication β Provide real-time visibility to support leads β Build a historical SLA performance dataset
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.
| Workflow | Proactive SLA monitoring & ticket escalation with Zendesk, Slack and Google Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 26 |
| Categories | Ticket Management |
| Author | Rahul Joshi |
| Published | 17 Oct 2025 |
Use the JSON export at /data/workflows/9829/9829.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management use case.