Message - Riggery

Live Chat and connected Telegram. Catalog line: Live chat and connected messengers. Start on Overview is required for Telegram. Live Chat in the app does not need it. See Listening. Bind the bot on Connections. Use two Message triggers with different Sources to route Telegram and Live separately.

Input

Inspector Settings. Empty-field rules for the Graph: Previous nodes.

Field	Required	Empty	Notes
Kind	Yes	—	Message.
Sources	No	Default: every source	Checkboxes Live and Telegram. Uncheck to limit this branch.
Inbound files	No	Default: Artifact only	Telegram attachments. Live Chat ignores this policy. Inbound files.

Output

Menu and empty fields: Previous nodes. Tokens below: one Trigger on the Graph (Trigger).

Output	In menu	Token	Type	Next node gets
Message text	Yes	`{{Trigger.text}}`	Text	Chat or Telegram body. Also the Result.
Photos	Yes	`{{Trigger.photos}}`	JSON array	Photo attachments. Not a File id. Photos and Files.
Files	Yes	`{{Trigger.files}}`	JSON array	File attachments.
Sender	Yes	`{{Trigger.from}}`	Text	Display name.
Chat ID	Yes	`{{Trigger.chatId}}`	Text	Telegram chat id. Empty on Live.
Message ID	Yes	`{{Trigger.messageId}}`	Text	Telegram message id (digits as text).
Sender user ID	Yes	`{{Trigger.fromUserId}}`	Text	Telegram user id.
Chat type	Yes	`{{Trigger.chatType}}`	Text	Telegram chat type (`private`, …).
Update ID	Yes	`{{Trigger.updateId}}`	Text	Telegram update id.
Memory / State rows	No	—	—	Written by Inbound files, not Previous nodes.

⌘I