Telegram Album Send
Explicit TDLib album send for a bot or user Account through its project communication profile.
Telegram bot and user Accounts with one managed TDLib session per Account.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
17 matching actions
Explicit TDLib album send for a bot or user Account through its project communication profile.
Explicit TDLib callback answer for a bot Account through its project communication profile.
Explicit TDLib chat inspect for a bot or user Account through its project communication profile. Returns bounded chat and membership facts. Use action.run with response_mode=raw and no idempotency key for this transient read.
Read one bounded page of a connected user Account's Main or Archive chats from TDLib. The cursor slices TDLib's current ordered list; chat reordering can shift pages. No chat messages are stored by this action. Use action.run with response_mode=raw and no idempotency key to receive this transient page.
Explicit TDLib chat resolve for a bot or user Account through its project communication profile. Returns a bounded chat summary. Use action.run with response_mode=raw and no idempotency key for this transient read.
Read the selected and available TDLib sender identities for one chat through a connected bot or user Account. Use a returned sender_ref on a later explicit send when choosing to post as a channel. Use action.run with response_mode=raw and no idempotency key for this transient read.
Explicit TDLib file download for a bot or user Account through its project communication profile.
Explicit TDLib identity get for a bot or user Account through its project communication profile.
Explicit TDLib message broadcast for a bot or user Account through its project communication profile.
Explicit TDLib message delete for a bot or user Account through its project communication profile.
Explicit TDLib message edit for a bot or user Account through its project communication profile.
Explicit TDLib message forward for a bot or user Account through its project communication profile.
Explicit TDLib message get for a bot or user Account through its project communication profile. Returns selected text and account-qualified file refs without the full native message object. Use action.run with response_mode=raw and no idempotency key for this transient read.
Read one bounded, newest-first TDLib history page from a known user Account chat. Pass next_before_message_id as before_message_id for the next page; a short page is not proof of the end. Full text requires include_content. No fetched messages are stored as communication resources by this action. Use action.run with response_mode=raw and no idempotency key to receive this transient page.
Explicit TDLib message react for a bot or user Account through its project communication profile.
Explicit TDLib message send for a bot or user Account through its project communication profile.
Explicit TDLib poll stop for a bot or user Account through its project communication profile.
Direct answer
People continue using Telegram as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 17 Telegram actions across Messaging. The exact actions used depend on the workflow and approval rules.
No. Telegram remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.