Telegram to Freshdesk, every message becomes a ticket
Your Telegram support channel feels “fast” until it turns into a scrolling wall of issues. A refund request gets buried under three complaints, someone replies in-thread, and suddenly you are hunting for context instead of solving the problem.
Support leads usually spot this first. Then it hits the ops manager who needs visibility, and the agency owner managing multiple client inboxes. This Telegram Freshdesk tickets automation turns every relevant message into a tracked case, so you stop losing follow-ups and start closing them.
You’ll see how the workflow tags refund vs. complaint messages, creates Freshdesk tickets automatically, replies to the customer in Telegram, and logs the case in Monday.com for tracking.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram to Freshdesk, every message becomes a ticket
flowchart LR
subgraph sg0["Telegram Intake Hook Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram Intake Hook"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/mondayCom.svg' width='40' height='40' /></div><br/>Log Refund in Monday"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/mondayCom.svg' width='40' height='40' /></div><br/>Log Complaint in Monday"]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Send Refund Acknowledgment"]
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Refund Keyword Check", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/freshdesk.svg' width='40' height='40' /></div><br/>Create Refund Ticket"]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/freshdesk.svg' width='40' height='40' /></div><br/>Create Complaint Ticket"]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Send Complaint Reply"]
n4 --> n5
n4 --> n6
n3 --> n1
n5 --> n3
n7 --> n2
n6 --> n7
n0 --> n4
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n4 decision
classDef customIcon fill:none,stroke:none
class n0,n1,n2,n3,n5,n6,n7 customIcon
The Problem: Telegram Support Messages Don’t Stay Trackable
Telegram is great for quick conversations. It’s not great for support accountability. Messages arrive in bursts, replies get split across threads, and the “important” stuff depends on someone noticing it in time. Refund requests are especially risky because they usually come with urgency, emotion, and sometimes a payment deadline. Complaints are just as dangerous, because the longer they sit, the more likely you lose the customer (or get a public review later). If your team is copying messages into a helpdesk manually, you’re also creating a new problem: inconsistent ticket details and missed context.
It adds up fast. Here’s where it breaks down in real teams.
- Someone has to notice and triage each Telegram message, which is easy to miss during busy hours.
- Manually creating Freshdesk tickets leads to messy subjects, missing tags, and duplicate cases.
- Customers don’t get confirmation, so they follow up again and the chat gets even noisier.
- There’s no lightweight tracking layer for the rest of the team, so status updates live in people’s heads.
The Solution: Turn Telegram Messages into Tagged Freshdesk Tickets
This workflow watches your Telegram support channel and instantly triages messages based on keywords. When a message looks like a refund request, it creates a Freshdesk ticket marked for refunds, then sends a short acknowledgment back to the customer in Telegram so they know they were heard. If the message matches complaint language instead, it creates a complaint ticket in Freshdesk and replies with the appropriate response. In both cases, the workflow also logs the event in Monday.com, which gives you an extra tracking view for the wider team (especially helpful if support is shared across ops, account management, or fulfillment). The result is simple: Telegram stays your intake channel, but Freshdesk becomes your system of record.
The workflow starts with a Telegram Trigger, then checks the message content with an If condition. From there it routes to “refund” or “complaint,” creates the right Freshdesk ticket, replies in Telegram, and finally logs the item in Monday.com.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your Telegram channel gets about 20 support messages a day, and around half need a ticket. Manually, creating 10 tickets at roughly 5 minutes each is close to an hour daily, plus context switching and the inevitable missed one. With this workflow, the “work” is basically zero: the message triggers instantly, Freshdesk tickets are created in the background, and the customer gets a reply right away. You get back about an hour a day, and cases stop slipping through the cracks.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram for the support intake channel
- Freshdesk to store and manage tickets
- Monday.com API token (get it from Monday.com Admin → API)
Skill level: Beginner. You’ll connect accounts, set keywords, and test with a few sample messages.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Telegram message triggers the workflow. A new message in your Telegram support channel kicks everything off, so nothing depends on someone being online.
The message is classified as refund or complaint. An If check looks for the keywords you define (for example: “refund,” “chargeback,” “cancel,” or “angry,” “broken,” “scam”). Keep it simple at first. You can always tighten it later.
Freshdesk tickets are created with the right context. Refund messages route to a refund ticket; complaint messages route to a complaint ticket. Because the workflow controls the structure, your subjects, tags, and descriptions stop being a free-for-all.
The customer gets a Telegram reply, and Monday.com gets a tracking item. The workflow sends a fast acknowledgment that sets expectations, then creates the matching record in Monday.com so your team can track volume and status without digging through chats.
You can easily modify the keyword logic to add more categories (billing, bug, feature request) based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Telegram Trigger
Set up the incoming Telegram message trigger that starts the workflow.
- Add the Telegram Intake Hook node as your trigger.
- Set Updates to
message. - Credential Required: Connect your telegramApi credentials in Telegram Intake Hook.
Step 2: Connect Freshdesk
Create tickets in Freshdesk based on the message type.
- Add Create Refund Ticket and set Options → Tags to
refund. - Set Options → Subject to
={{$node["Refund Keyword Check"].json["message"]["text"]}}. - Set Requester to
emailand leave Requester Identification Value empty unless you plan to map it later. - Add Create Complaint Ticket and set Options → Tags to
complaint. - Set Options → Subject to
={{$node["Refund Keyword Check"].json["message"]["text"]}}. - Credential Required: Connect your freshdeskApi credentials in both Create Refund Ticket and Create Complaint Ticket.
Step 3: Set Up Routing Logic
Use a keyword check to route messages into refund or complaint paths.
- Add the Refund Keyword Check node after Telegram Intake Hook.
- Configure the condition: Value 1 to
={{$node["Telegram Intake Hook"].json["message"]["text"]}}, Operation tocontains, and Value 2 torefund. - Connect the true output to Create Refund Ticket and the false output to Create Complaint Ticket. Refund Keyword Check outputs to both Create Refund Ticket and Create Complaint Ticket in parallel.
Step 4: Configure Output and Logging Nodes
Send acknowledgments to Telegram and log ticket creation to Monday.com.
- In Send Refund Acknowledgment, set Text to
Hi, thanks for sending this. We will review your request for refund as soon as possible 💶 💵 💷and Chat ID to={{$node["Telegram Intake Hook"].json["message"]["chat"]["id"]}}. - Credential Required: Connect your telegramApi credentials in Send Refund Acknowledgment and Send Complaint Reply.
- In Send Complaint Reply, set Text to
Hi, thanks for sending this. We will review your complaint as soon as possible 📬 ☀️ ✅and Chat ID to={{$node["Telegram Intake Hook"].json["message"]["chat"]["id"]}}. - In Log Refund in Monday, set Name to
={{$node["Create Refund Ticket"].json["subject"]}}, Board ID to[YOUR_ID], Group ID tonew_group, and Resource toboardItem. - In Log Complaint in Monday, set Name to
={{$node["Telegram Intake Hook"].json["message"]["text"]}}, Board ID to[YOUR_ID], Group ID totopics, and Resource toboardItem. - Credential Required: Connect your mondayComApi credentials in both Log Refund in Monday and Log Complaint in Monday.
[YOUR_ID] with your actual Monday.com board ID in both Monday nodes or the items will fail to create.Step 5: Test and Activate Your Workflow
Validate the routing logic and confirm tickets, replies, and logs are created correctly.
- Click Execute Workflow and send a Telegram message that contains the word
refundto trigger the refund path. - Confirm that Create Refund Ticket creates a Freshdesk ticket, Send Refund Acknowledgment replies in Telegram, and Log Refund in Monday creates an item.
- Send a Telegram message that does not include
refundto trigger the complaint path and verify Create Complaint Ticket, Send Complaint Reply, and Log Complaint in Monday. - When successful, toggle the workflow to Active for production use.
Common Gotchas
- Freshdesk credentials can expire or need specific permissions. If things break, check your Freshdesk API key and agent access settings first.
- Telegram bots must be in the right chat with permission to read messages. If the trigger is silent, verify the bot is added to the support channel and privacy mode is configured correctly.
- Monday.com board structure matters. If the “log item” step fails, it’s usually a column mismatch or a missing required field on the board.
Frequently Asked Questions
About 30 minutes if you already have Freshdesk and Telegram access set up.
No. You’ll mostly connect accounts and edit the keyword checks. Testing a few sample messages is the “hardest” part.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Freshdesk and Monday.com plan costs if your account requires API access.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should if your channel has mixed requests. Add more If branches after the Telegram trigger (for billing, bugs, feature requests), then point each branch to its own Freshdesk “Create Ticket” action with a dedicated tag. You can also swap the keyword check for an AI Agent classifier if your messages are messy or multilingual. Common tweaks include setting priority for “urgent” keywords, changing the Telegram reply text, and logging extra fields to Monday.com.
Usually it’s an expired or incorrect API key, or the agent account doesn’t have permission to create tickets. Update the Freshdesk credentials inside n8n and confirm the user can create tickets in your Freshdesk admin. If it fails only during busy periods, you might be hitting rate limits and should slow down message processing or reduce retries.
A lot for typical small teams, and it mostly comes down to your n8n plan and API limits.
For this workflow, n8n has a few advantages: more complex routing with branching logic, a self-hosting option for unlimited executions, and a workflow structure that’s easier to extend as your tagging rules grow. Zapier or Make can be fine for simple “message → ticket” flows, but keyword-based classification plus different replies and Monday.com logging can get awkward (and expensive) fast. If you’re already paying for Zapier and want the quickest possible setup, it may be “good enough” for a while. If you want control and room to grow, n8n is the safer bet. Talk to an automation expert if you want help choosing.
Once this is running, Telegram becomes a clean intake channel again, not your accidental ticket queue. The workflow handles the repetitive sorting and logging so your team can focus on closing cases.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
