Block 1 - 01 Telegram Trigger: Intake + Status
- Type / Role
- n8n-nodes-base.telegramTrigger - telegramTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
Telegram ticket intake and status tracking with Postgres Who’s it for Anyone running support requests through Telegram, Email, Webhooks, and so on who needs a lightweight ticketing system without p...
n8n-nodes-base.telegramtrigger, n8n-nodes-base.switch, n8n-nodes-base.code, n8n-nodes-base.postgres, n8n-nodes-base.telegram, n8n-nodes-base.if, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mohammad.
Original n8n.io sourceAnyone 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 that want tickets logged in a structured database (Postgres) and tracked automatically. I'm using Telegram since it's the most convenient one.
This workflow turns (Telegram) into a support desk:
tickets table:CREATE TABLE tickets (
id BIGSERIAL PRIMARY KEY,
correlation_id UUID,
source TEXT,
external_id TEXT,
requester_name TEXT,
requester_email TEXT,
requester_phone TEXT,
subject TEXT,
description TEXT,
status TEXT,
priority TEXT,
dedupe_key TEXT,
chat_id TEXT,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP DEFAULT NOW()
);
/new in Telegram and follow the prompts.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 45 workflow blocks. Download the JSON for the full node graph.
| Workflow | Lightweight support desk with Telegram and Postgres database tracking |
|---|---|
| Complexity | advanced |
| Nodes | 45 |
| Categories | Content Creation, Ticket Management |
| Author | Mohammad |
| Published | 20 Sept 2025 |
Use the JSON export at /data/workflows/8789/8789.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.
Telegram ticket intake and status tracking with Postgres Who’s it for Anyone running support requests through Telegram, Email, Webhooks, and so on who needs a lightweight ticketing system without p...
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 Content Creation, Ticket Management use case.