Product Docs
TG Dock Documentation
This hub is designed for operators and support teams who need fast, action-oriented guidance for the TG Dock interface.
Built for operations
The docs favor practical workflows, decision points, and operational guardrails instead of long conceptual manuals.
Browse all sections
Start
Documentation
Public knowledge base for TG Dock covering onboarding, accounts, tasks, pipelines, proxies, and diagnostics.
Getting Started
The first path through TG Dock: menu structure, first-run order, and trial-user limits.
Settings
User profile, plans and limits, Telegram credentials, preferences, and security settings.
Operations
Overview
The main monitoring dashboard for TG Dock with quick links, activity charts, queue states, and proxy health.
Imports
Upload Telegram accounts, track file processing, and re-open import runs from a single history view.
Accounts
Inspect account readiness, authorize Telegram sessions, assign proxies, and manage account metadata.
Tasks
Create one-off Telegram actions, filter run history, and inspect structured execution results.
Automation
Pipelines
Build multi-step TG Dock automations with delays, target sources, error rules, and execution diagnostics.
Dictionaries
Shared contact and chat dictionaries reused across tasks and pipelines.
Proxies
Create, validate, enable, disable, and batch-bind proxies to accounts inside TG Dock.
Documentation map
The library is organized by interface area so teams can jump straight into the screen they are using.
Longer flows such as pipeline building and proxy batch binding are split into guided sections with screenshots.
- Getting Started for first-run onboarding and trial limits.
- Overview, Imports, Accounts, and Tasks for daily execution.
- Pipelines and Proxies for advanced operations.
- Warmup, System Log, and Settings for control and diagnostics.
Fastest paths
Set up a fresh workspace
Start with Getting Started, then move to Settings, Imports, and Accounts.
Run your first Telegram action
Verify account readiness in Accounts and create a single execution in Tasks.
Build a repeatable flow
Use Pipelines when an operation needs sequencing, delays, and error policies.