How krau/saveany-bot works
Save Any Bot accepts Telegram messages and API requests, turns selected files, links, or transfer requests into tasks, and saves the resulting content to configured storage. The main stages are request handling, task execution or parsing/downloading, and storage upload; Telegram watching and the HTTP API are additional entry points. Storage backends are registered behind a shared interface. The README documents capabilities whose implementation was not sampled; edges based on it are identified accordingly, and unsampled internals are not inferred.
Main entry points: tasks Task engines · core.go Task coordinator · storage.go Storage registry · handlers Bot handlers
Components 21
Entry points
- Bot handlers
client/bot/handlers - Chat watcher
client/user/watch.go - HTTP API
api/handlers.go - API server
api/server.go
Task processing
- Task coordinator
core/core.go - Task engines
core/tasks - Site parsers
parsers/parser.go - Aria2 downloader
pkg/aria2/client.go - yt-dlp downloads
core/tasks/ytdlp - Telegraph handling
core/tasks/telegraph
Storage
- Storage registry
storage/storage.go - Local storage
storage/local/local.go - Cloud backends
storage/alist/alist.go - Telegram storage
storage/telegram/telegram.go
Configuration and state
- Persistent data
database/db.go - Configuration
config
Other components
- Telegram user
- API caller
- Telegram
- Websites and URLs
- Storage services
Connections 23
- Telegram user → Bot handlers: sends requests
- Bot handlers → Task coordinator: submits tasks
- Telegram user → Chat watcher: posts media
- Chat watcher → Task coordinator: auto-saves
- API caller → API server: sends requests
api/server.go - API server → HTTP API: routes requests
api/server.go - HTTP API → Task coordinator: creates tasks
api/handlers.go - Bot handlers → Task coordinator: cancels tasks
client/bot/handlers/tasks.go - Task coordinator → Task engines: dispatches tasks
- Task engines → Storage registry: saves results
- Task engines → Site parsers: parses links
- Task engines → Aria2 downloader: downloads URLs
- Task engines → yt-dlp downloads: downloads media
- Task engines → Telegraph handling: handles pages
- Storage registry → Local storage: constructs backend
storage/storage.go - Storage registry → Cloud backends: constructs backend
storage/storage.go - Storage registry → Telegram storage: constructs backend
storage/storage.go - Local storage → Storage services: writes files
- Cloud backends → Storage services: writes files
- Telegram storage → Telegram: uploads media
storage/telegram/telegram.go - Site parsers → Websites and URLs: fetches content
- Configuration → Storage registry: configures backends
storage/storage.go - Task coordinator → Persistent data: uses task state