Glossary
Telegram-Auto glossary
Quickly look up concepts used in the interface, API, and account operations.
The terms below describe how Telegram-Auto organizes accounts, assigns jobs, and communicates with external systems. The English terms in brackets help you cross-reference the API or diagnostic information.
Some concepts belong to different layers: a machine can be online while a session needs sign-in again, or an account can have a valid session but be held by its safety state.
Accounts and permissions
| Term | Definition |
|---|---|
| Workspace | A team's shared data and permission boundary in the app. |
| Owner | The workspace owner role, with administrative permissions reserved for it on specific operations. |
| Manager | A role allowed to manage operations within the scope defined by the app. |
| Support | Reads and replies in Inbox on allowed accounts; does not manage infrastructure. Not an AI agent. |
| Viewer | Sees only Overview and Stats; cannot read messages. |
| Personal account | A Telegram account signed in to perform the user's work. |
| Internal account | An account marked as belonging to the team and excluded from discovery and outreach flows. |
| Sign-in session [Session] | Authentication data that lets the worker continue accessing a Telegram account. |
| Two-step verification password | A password Telegram requires in addition to the sign-in code in flows that need verification. |
| Principal | The identity the server uses to evaluate a person's or connection's permissions. |
Machines and safety conditions
| Term | Definition |
|---|---|
| Machine [Node] | A Hetzner or Windows machine registered to run a worker. |
| Worker | The program on a machine that executes jobs assigned by the server. |
| Heartbeat | Periodic information showing that the worker is still communicating with the server. |
| Proxy | A dedicated network route attached to an account for connecting to Telegram. |
| Observed IP | The IP address actually seen through the proxy during a check. |
| Safety gate | Where the server checks conditions before assigning a job to a worker. |
| Free | A quota mode that lets you set your own limits without removing safety checks. |
| Safe | A mode using the app's standard quotas, warm-up, and activity schedule. |
| Warm-up | A mechanism that adjusts activity according to the account's stage. |
| Quota | The allowed activity level, calculated from recorded actions. |
| Safety state | A state reflecting throttling, restriction, freezing, or ban signals. |
| Session state | A separate state showing whether the account is signed in or needs authentication again. |
| Wait requirement [FLOOD_WAIT] | A Telegram response requiring the relevant type of action to be deferred. |
| Slow mode [SLOWMODE] | A message interval enforced by a Telegram group. |
| Outreach restriction [PEER_FLOOD] | A Telegram signal that causes the app to mark the account as restricted. |
| Do not contact | A mechanism that prevents outreach to people excluded within the workspace. |
Jobs and Inbox
| Term | Definition |
|---|---|
| Job | A unit of work queued for a worker to execute. |
| Held | A condition where a job cannot run because some requirements are not met. |
| Lease | A time-limited right for a worker to execute an assigned job. |
| Unverified | A condition where an effect may have occurred but there is not enough evidence to confirm it. |
| Reconciliation | The process of finding evidence from Telegram to clarify a result. |
| Late receipt | Evidence arriving later that helps confirm an eligible execution. |
| Redrive | Creating a new job from an eligible old job, with permissions and safety checked again. |
| Conversation | A message thread between an account and a Telegram user, group, or channel. |
| Template | Content written by a person for reuse in sends. |
| Campaign | A set of outreach jobs using configured content, recipients, and progression. |
Integrations
| Term | Definition |
|---|---|
| AI connection | A separate integration identity with an assigned role, scope, and budget. |
| Scope | A specific group of permissions a connection may use. |
| Operation | An action declared in the shared registry so REST and MCP use the same rules. |
| MCP tool | A way for external systems to discover or call operations through MCP. |
| Idempotency key | A value that helps repeated calls receive the same result rather than creating unintended extra effects. |
| Confirmation token | A single-use token bound to the connection, operation, and input that require approval. |
| Webhook | A mechanism for sending signed events to a receiver's address. |
| Delivery | A delivery of an event to one webhook, which may include multiple attempts. |
| Event replay [Replay] | Creating new deliveries for old events within a selected scope. |
| Secret sealing [Sealing] | Protecting secrets with encryption bound to their usage context. |