Listening
Start turns incoming Telegram, a Telegram account, cron, webhook, and IMAP on. Stop turns them off. Start can be blocked: no runnable Graph, compatibility errors on the pinned Graph, or nothing ready (add Cron, Webhook, or IMAP poll, or a Telegram trigger plus a bot token).Triggers table
The Triggers table lists Cron, Webhook, IMAP, Telegram, Telegram account, and Live on the active Graph. Status is ready or needs setup (or bot claimed elsewhere). Empty table: No triggers on the active graph. If the Graph hastelegram.send or imap.fetch and no inbound Telegram or IMAP trigger, a second table Used by tools lists those adapters.
Last activity
Last activity is the last check while listening is on. After Start, before the first poll: Waiting for the first poll…. Idle poll rows can say idle. A dash means there is nothing to show yet.Version
The workspace badge is Live · vN when this Instance is pinned, or Draft. A newer published version shows the banner New version available: vN with Update to vN. Use draft (Graph owners) is on the Live · vN badge. It clears the pin so Chat and listening use the draft Graph.Telegram
Configure on the Telegram row. Telegram bot token, Reply in Telegram with the agent output, and When to reply. When to reply uses the same choices as a Telegram account, for Private and Group only. There is no channel, and a chat has no topics. A reply to this bot counts as a mention. Add a chat finds chats that have already written to this bot, after at least two characters. A private chat whose Starts you set to Every message lets that person talk and creates them in People, including when Who can talk is Owner only. The bot has no action that adds or removes a chat. With The agent chooses, a successful send listens to that whole chat for the time under Listen after the agent’s last message for. Don’t reply also stops Reply in Telegram with the agent output, the failure notice, and the busy reply in that chat. Until you save a policy, a private chat starts a Run and the agent can reply. A group starts a Run when someone mentions this bot or replies to it. The private chat of the person linked as Owner always starts a Run, and the agent can reply there. In a group, that person follows the group rule. A message starts a Run. In a group set to Only when mentioned, other messages that arrive with it stay in that Run and do not start one alone. Messages that arrive while a Run is still going wait and start together after it finishes. With Reply in Telegram with the agent output on, that text is sent when the Run finishes, unless this chat may not be written to. If the chat already has too many messages waiting, the bot sends one message until there is room again. The bot does not report that the Run failed because it took a long time. Typing is Off, When sending, or Pace by length. It appears when a message is sent, not while the agent is working. Pace by length waits in proportion to the text, at Typing speed, and never longer than Max delay. 0 uses the platform limit. Default max delay is 8 seconds. Save Telegram. Secrets use{{secret:…}}. Link people on People — otherwise unlinked chats cannot start a Run.
telegram.send can set its own token on the node. Empty uses this Instance bot.
Telegram account
Configure on the Telegram account row.- Open my.telegram.org and sign in.
- Open API development tools.
- Create an application if you do not have one. Copy App api_id and App api_hash.
- Paste them into API ID and API hash, then Save.
- Sign in with QR. In Telegram open Settings → Devices → Link Desktop Device and scan the code. Or choose Use a phone number, then the code Telegram sends and a cloud password when Telegram asks for one.
When to reply
When to reply sets where a message starts a Run, and where the agent may send.- Private chats and mentions. A private chat starts a Run, and the agent can reply. A group starts a Run when someone mentions this account. A channel stays quiet until you add it. The agent can reply there. The agent cannot change the list.
- Listen, don’t reply. Those same chats start a Run. The agent does not reply.
- The agent chooses. A chat starts a Run after the agent writes there, or when the agent adds it. Chats you add stay as you set them.
- Only chats you add. A Run starts only in the chats you add. The agent cannot write anywhere else.
- Custom. Private, Group, and Channel each have Starts and Replies.
Daily limits
Messages per day and Joins per day take a whole number, or stay empty for no limit. Messages accept 1 to 5000. Joins accept 1 to 200. The line under a field is how many went out today. The count resets at 00:00 UTC. The time on the panel is in your timezone. A text message counts as one. Each file in an album counts as one. A sticker, an inline result, and a poll each count as one. Each forwarded message counts as one. If the whole album or forward would pass the number left today, nothing is sent. Reactions, edits, votes, button clicks, pins, moderation, stories, and profile changes do not count. Saved Messages do not count. A reply sent while someone links a chat does not count. Joins per day counts joining a chat. The Telegram bot on this Instance is separate and is not part of these limits. If Telegram asks the account to wait more than 10 seconds, the panel says sending or joining is paused until a time. A send or join before then fails. After a wait of 10 seconds or less, the send is tried again. Sign in again to drop a pause left by the previous sign-in. Slow mode in one chat does not pause the account. That send fails with the wait time and does not count. Disconnect signs the account out and keeps API ID, API hash, and the chat rules. Signing in a different Telegram account removes those rules. One Telegram account can be connected to one Instance. If it is already connected elsewhere, sign out there first. Tools: Telegram account.IMAP
Configure on the IMAP row. Host, Port, TLS / SSL, User, Password, and Folder. IMAP poll and optional IMAP fetch use this when those fields on the node are empty. Save IMAP.Shared mailbox
If several Instances use the same IMAP inbox, Shared mailbox is in the IMAP panel:- Shared — each Watching Instance gets the mail. Emails stay unread until every watching template finishes successfully.
- Only this Instance — Emails are marked read after this template succeeds.