Skip to main content
Triggers turns incoming Triggers on and off for this Instance. Start / Stop are on this tab. Chat in the app does not need Start. See Listening. Configure opens a side panel for Telegram, a Telegram account, IMAP, or webhook.

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).
Stop listening before Update to vN or Use draft. Those actions stay disabled while listening is on.

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 has telegram.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.
  1. Open my.telegram.org and sign in.
  2. Open API development tools.
  3. Create an application if you do not have one. Copy App api_id and App api_hash.
  4. Paste them into API ID and API hash, then Save.
  5. 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.
One phone number can create one application. Paste that same API ID and API hash into another Instance you own. After Save, API hash shows Saved. Leave the field empty to keep it. Saving a new API ID or API hash while signed in disconnects the account. After you sign in, the account name and Disconnect are at the top. Open Sending for Replies, Typing, and Daily limits. Open Application to change API ID or API hash. Save stores these together.

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.
When Starts is Only when mentioned, a reply to a message from this account also starts a Run. Follow the rule shows that rule in parentheses. Choosing it for both Starts and Replies removes the row. The agent can is Change nothing, Add its own chats, or Add and remove its own chats. The agent never changes a chat you set. With either of the last two, the agent can put a chat into Chats so messages from it start the agent. The agent can add a chat for up to is how long such a chat stays there, from 5 minutes to 30 days. When the agent does not name a time, this one is used. After it ends, the chat leaves Chats and follows When to reply again. The agent can add a chat with no end lets the agent keep a chat there without an end. Listen to chats the agent writes to adds a chat to Chats, marked Agent, when the agent writes there, so replies from it start the agent. Listen after the agent’s last message for is how long it listens. If the agent writes there again, the time counts from the new message. It cannot be longer than The agent can add a chat for up to. Chats lists the rows that differ from that rule. Add a chat searches Telegram after you type at least two characters and pause. Pick a chat, then set Starts and Replies, and Save. 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. Saving applies to the whole chat and replaces its topic rows. A topic row wins over the row for the whole chat. A saved row shows the name, and under it the type, General or Topic, You or Agent, and Until when the row ends. Starts is Every message, Only when mentioned, Don’t start, or Follow the rule. Only when mentioned is not offered for a private chat. Replies is Can reply, Don’t reply, or Follow the rule. Don’t reply also stops Reply immediately in that chat. Changing a row the agent added makes it yours and removes the time limit. When the agent has rows, the list can show All, Mine, or Agent’s, and Remove the agent’s chats removes only those. Search this list matches the name or id when the list is long. Saved Messages always start a Run, and the agent can reply there. A message from the Telegram account linked as Owner starts a Run in any chat. The agent can reply in that person’s private chat. The agent’s own sends do not start a Run. The chat is marked read up to the accepted message, including older messages in that chat. Reply immediately posts the Run text in that chat when the Run finishes. Only when the agent sends still starts the Run and marks the chat read, but Telegram receives only a message the agent sends. Typing follows the same Off / When sending / Pace by length settings as the bot, and appears only while that text is being sent. The next Run in that chat sees the messages people sent and the text that was delivered there. A reply that was not sent is left out. Older messages in Telegram are still read with Read messages in a chat. Messages that arrive together are read as one Run. While a Run is still going, later messages in that chat wait and start together after it finishes.

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.
Also watching lists other copies. Starting while others already watch this inbox asks how to share: Process in parallel (shared) or Only this Instance. If another Instance is already Only this Instance, stop listening there first.

Webhook

Configure on the Webhook row. Start listening to issue the URL and signing secret. Endpoint URL is the HTTPS address for POST. Rotate secret shows Signing secret once. Rotate URL replaces the path. Last delivery time, or No deliveries yet. How to call it: Webhook.