AutomationFlowsSlack & Telegram › Support & Ticketing

Support & Ticketing workflows.

Support & Ticketing workflows in the Slack & Telegram category. 34 curated automations — all importable into your n8n instance in one click.

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
Slack & Telegram

Anyone running support requests through Telegram, Email, Webhooks, and so on who needs a lightweight ticketing system without paying Zendesk prices. Ideal for small teams, freelancers, or businesses t

Telegram Trigger, Postgres, Telegram
Slack & Telegram

This workflow is built for education businesses, course creators, coaching programs, and online academies that use Close CRM for sales and need to automate everything that happens after a deal closes.

Slack, HTTP Request, Airtable
Slack & Telegram

Automates the forwarding of messages from WhatsApp (via Evolution API) to Chatwoot, enabling seamless integration between external WhatsApp users and internal Chatwoot agents. It supports both text an

Execute Workflow Trigger, Redis, N8N Nodes Evolution Api +3
Slack & Telegram

Empower your property management with a high-efficiency automated support desk. This workflow manages the complete maintenance lifecycle—from initial issue classification and ticket creation to team a

Google Sheets, N8N Nodes Wati
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

[STG] Match Diário. Uses slack, httpRequest, postgres, zendesk. Scheduled trigger; 24 nodes.

Slack, HTTP Request, Postgres +2
Slack & Telegram

This template helps you create an interactive InfraNodus knowledge graph for your ZenDesk tickets using any search criteria (e.g. after a certain date, specific status, sender, keyword) that will auto

Zendesk, HTTP Request, Telegram +4
Slack & Telegram

Stay on top of your support pipeline with this Ticket Status Digest automation for Zendesk. Built in n8n, this workflow automatically fetches tickets from Zendesk, filters only open ones, enriches the

Google Sheets, Slack, Zendesk
Slack & Telegram

This workflow automates the prioritization and escalation of customer support tickets. It acts as an intelligent triage system that identifies high-value customers and potential churn risks in HubSpot

HTTP Request, HubSpot, Jira +1
Slack & Telegram

Analyze_Crowdstrike_Detections__search_for_IOCs_in_VirusTotal__create_a_ticket_in_Jira_and_post_a_message_in_Slack. Uses scheduleTrigger, itemLists, httpRequest, splitInBatches. Scheduled trigger; 18

Item Lists, HTTP Request, Jira +1
Slack & Telegram

This n8n workflow automates the handling of security detections from CrowdStrike, streamlining incident response and notification processes. The workflow is triggered daily at midnight by the Schedule

Item Lists, HTTP Request, Jira +1
Slack & Telegram

This workflow detects ticket classification events in Beex where the communication channel was WhatsApp, extracts the messages from the interaction, and logs them as activity in the corresponding HubS

N8N Nodes Beex, HubSpot, HTTP Request
Slack & Telegram

How it works This AI Customer Success Risk Prediction workflow revolutionizes customer retention by predicting churn risk 30-90 days before it happens. Here's the high-level flow: Daily Data Collectio

HTTP Request, Zendesk, Stripe +4
Slack & Telegram

Customer support managers and team leads Customer success teams monitoring satisfaction Product managers analyzing user feedback Business analysts measuring support metrics Operations managers optimiz

N8N Nodes Scrapegraphai, Google Sheets, Slack
Slack & Telegram

This workflow starts when a user triggers a custom slash command in Slack. The workflow checks if a valid message (email address or HubSpot contact ID) was provided. Based on the input, it searches Hu

Stop And Error, HubSpot, Slack
Slack & Telegram

Accelerate VIP support handling with this n8n workflow template that automatically identifies high-priority customers and ensures their tickets get instant attention.

ClickUp, Telegram, Zendesk
Slack & Telegram

⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n ins

N8N Nodes Scrapegraphai, Matrix, Intercom
Slack & Telegram

Code. Uses zendesk, slack, stickyNote. Webhook trigger; 9 nodes.

Zendesk, Slack
Slack & Telegram

This workflow creates a Slack thread when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as replies to the thread in Slack. Zendesk account and Zendesk cred

Zendesk, Slack
Slack & Telegram

Telegram Mondaycom. Uses telegramTrigger, mondayCom, telegram, freshdesk. Event-driven trigger; 8 nodes.

Telegram Trigger, Monday.com, Telegram +1
Slack & Telegram

Zendesk-to-slack. Uses manualTrigger, slack, zendesk. Event-driven trigger; 5 nodes.

Slack, Zendesk
Slack & Telegram

Auto-create Jira tickets from n8n workflow failures. Uses jira, slack. Webhook trigger; 8 nodes.

Jira, Slack
Slack & Telegram

> This workflow uses the Vtiger CRM community node. To use it, you must be running a self-hosted version of n8n with Community Nodes enabled. Go to → Click Install Node Enter the package name: Rest

N8N Nodes Vtiger Crm, Telegram
Slack & Telegram

Flow. Uses intercomTrigger, intercom, slack, mongoDb. Event-driven trigger; 7 nodes.

Intercom Trigger, Intercom, Slack +1
Slack & Telegram

Slack AI Helpdesk Bot. Uses slackTrigger, openAi, slack. Event-driven trigger; 3 nodes.

Slack Trigger, OpenAI, Slack

34 of 34 workflows in this view · Browse all →

FAQ

What is in the Support & Ticketing (Slack & Telegram) category?

All n8n workflows in the AutomationFlows catalog that automate support & ticketing (slack & telegram) use cases. 34 workflows live here, each integration-tagged and importable into a self-hosted or cloud n8n instance.

How do I use a Support & Ticketing (Slack & Telegram) workflow?

Open any workflow detail page, click 'Copy JSON', then in n8n go to Workflows → Import from File or paste into a new workflow. Add your credentials (the catalog strips them before publishing) and activate.

Are these workflows free?

Yes — the entire catalog is free to browse and copy. Pro adds a multi-signal QualityScore on every workflow plus bulk JSON download.