Get Received Telegram Message | Chatigram Documentation

Plan availability #

Feature	Free	Starter	Pro	Enterprise
Active workflows	3	10	45	Unlimited

Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.

When to use this node #

Retrieve messages that were received via webhook. Works with any connected Telegram bot (both regular and automation accounts). Messages are automatically received when webhooks are active. Perfect for cron-triggered workflows to check for new messages without API conflicts.

Add Get Received Telegram Message to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.

Before you begin #

Connect Telegram in App Connections first. Select the intended account in this node; an account connected to a different service is not interchangeable. Available actions depend on the permissions granted to that connection.

Configure the fields #

Field	What to enter
Telegram Bot	Any connected Telegram bot account (messages received when webhook is active)
Chat ID (Optional)	Filter messages from specific chat only. Leave empty to get latest message from any chat.
Limit (Optional)	Number of messages to retrieve (default: 1 for latest message) Example/default shown in the editor: `1`.
Mark as Processed	Enable to track this message as processed. Next call will detect if message is new or same as last processed one. (true/false) Choices: `false`, `true`. Example/default shown in the editor: `false`.
Processing Context (Optional)	Unique identifier for this processing workflow (default: 'default'). Use different contexts to track messages separately across different workflows. Example/default shown in the editor: `default`.

Use the result #

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

Output	Meaning / label
`updateId`	Update ID
`messageId`	Message ID
`messageText`	Message Text
`messageDate`	Message Date
`userId`	User ID
`userName`	User Name
`userFirstName`	User First Name
`userLastName`	User Last Name
`userIsBot`	User Is Bot
`chatId`	Chat ID
`chatType`	Chat Type
`chatTitle`	Chat Title
`chatUsername`	Chat Username
`isCommand`	Is Command
`commandName`	Command Name
`hasPhoto`	Has Photo
`hasDocument`	Has Document
`hasAudio`	Has Audio
`hasVideo`	Has Video
`newMembersCount`	New Members Count
`newMemberNames`	New Member Names
`isReply`	Is Reply (true/false)
`replyToUserId`	Replied-To User ID
`replyToUserName`	Replied-To Username
`replyToFirstName`	Replied-To First Name
`replyToMessageId`	Replied-To Message ID
`replyToMessageText`	Replied-To Message Text
`rawMessage`	Raw Message Data (JSON)
`isNewSinceLastCheck`	Is New Since Last Check
`guestQueryId`	Guest Query ID (use with Answer Guest Query node)
`isGuestMessage`	Is Guest Message (true/false)

Connect the next step #

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

Test it in a workflow #

Configure this node with a small, recognizable test input or a test resource.
Check the variables from preceding steps and the connection selected in the inspector.
Save the workflow. For event-driven flows, generate the actual event; use Run only for a Manual workflow.
Open Workflow Activity and check the outcome before enabling wider use.

If something goes wrong #

Reconnect the account if authorization has expired, then verify its permissions on the specific resource.
Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
Follow the troubleshooting guide for a symptom-by-symptom checklist.

Catalog coverage #

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.