n8n does not chat with your Telegram account, it schedules against it. Each row below is a real workflow shape: the trigger and goal on one side, the ordered Entergram calls that satisfy it on the other, and what lands in your systems when the run finishes. All of them run whether or not anyone has the tab open, which is the whole reason to build here instead of in a chat client.
The workflow
Nightly at 02:00, mirror every workspace chat and its pipeline fields into Postgres for the BI dashboard.
Tools called
entergram_list_workspace_chatsentergram_list_custom_columnsentergram_get_chat_custom_fields
The run produces
A Schedule Trigger fans the chat list into a Loop Over Items node, reads the column schema once so keys are resolved rather than guessed, then upserts a row per conversation. Your analysts query Telegram pipeline state in SQL the next morning without anyone touching Entergram.
The workflow
When CI posts a deploy-finished webhook, notify the customer groups affected by the release.
Tools called
entergram_list_groupsentergram_send_message
The run produces
A Webhook node receives the build payload, a Code node maps service names to the group titles that care about them, and one send call fires per group. Release comms stop depending on whoever remembers to paste the changelog, and because the message is composed from the build metadata it always carries the version that actually shipped.
The workflow
Hourly, close any ticket whose underlying conversation has been silent for seven days.
Tools called
entergram_list_ticketsentergram_list_messagesentergram_update_ticket
The run produces
The workflow pulls open tickets, checks the timestamp of the last message on each linked thread, and filters on age with an IF node before writing the status change. Stale queue items disappear on their own, and the ones that get a reply after closing simply reopen on the next inbound message.
The workflow
On a payment-failed event from your billing provider, open a dunning ticket with the invoice details attached.
Tools called
entergram_list_contactsentergram_create_ticketentergram_create_ticket_comment
The run produces
Contact lookup matches the payer to a Telegram conversation, the ticket is created against that chat, and the raw invoice payload goes in as a comment so the agent who picks it up has the amount and failure reason without opening the billing console. Dunning becomes a queue item with context attached rather than an email nobody owns.
The workflow
Every Sunday, reconcile Telegram group membership against the HR roster and remove people who have left.
Tools called
entergram_list_groupsentergram_list_group_membersentergram_remove_chat_member
The run produces
A Merge node diffs the two member lists and only the removals flow onward. Offboarding stops leaving ex-contractors sitting in client groups for months, and the run summary doubles as an access-review artefact for your auditor.
The workflow
Every fifteen minutes, forward invoices and contracts that clients dropped into chat to the finance channel.
Tools called
entergram_list_messagesentergram_get_messageentergram_forward_messages
The run produces
The polling branch scans recent history for document attachments, a Filter node keeps the ones matching your naming rules, and the forward preserves the original sender attribution. Finance stops asking whether the signed PDF is still sitting in someone's DMs.
