Telegram from your own account
Send your approved Outreach messages from your own Telegram account through the Venom daemon on your computer. You log in there, Venom Cloud never holds the login, and the daemon keeps the account under Telegram's limits.
The telegram_user channel sends from your personal Telegram account, so a message reaches someone who never wrote
to you first. A Telegram bot can't do that. Outreach uses it for a sequence step on Telegram: the message comes from
you, and replies land in your normal Telegram chats.
The login stays on your computer. The Venom daemon logs in to Telegram, keeps the session encrypted on disk, and sends each message when Venom Cloud asks it to. Venom Cloud never sees your phone number, the login code, your two-step verification password or the session. If Venom Cloud were breached, nobody could read your Telegram from there.
The cost is that your computer has to be on. While it is asleep or off, messages wait (see When your computer is off).
The Telegram helper
The Telegram connection runs in a small separate program, venom-telegram, installed next to the daemon. That keeps
the daemon itself small. The daemon starts the helper only after you log in, stops it within 15 seconds of a logout,
and talks to it only over a private socket in data/telegram/ that other users on the computer can't open. The helper
never sees the encryption key or the files: the daemon hands it the session and seals whatever comes back. The socket
carries two requests, each with a random token the daemon picks when it starts the helper: POST /helper/call for a
Telegram call (resolve, send, history), and GET /helper/events for new sessions and incoming messages. The helper
never listens on a network port.
The helper ships in the daemon's downloads (the archives, the macOS app and the .pkg installer) and in the release's
install.sh. It is not in the orchestrator's Docker image. To send from your own Telegram account, use the
desktop daemon, not an orchestrator in Docker.
If the helper is missing, venom-daemon telegram status and the card in Settings, Comms say "Telegram helper not
installed". Messages wait, and everything else keeps working. Reinstall the daemon to bring the helper back, or
point VENOM_TELEGRAM_HELPER at the venom-telegram binary if you keep it somewhere else.
Set it up
Install the Venom daemon and connect it to your org (Connect to Venom Cloud).
On that computer, log in to Telegram:
venom-daemon telegram loginIt asks for your phone number, then the code Telegram sends to your Telegram app (or by SMS), then your two-step verification password if you set one. The password is checked with Telegram's SRP exchange, so it never leaves your computer in clear. A wrong code or password asks again, three times. The running daemon picks up the new session within 15 seconds. At the end, the login prints a link code such as
K7QM2-X9PRT.In Venom Cloud, open Settings, Comms, Telegram (your account), type the link code and select Link.
The code only works for daemons your org enrolled itself. A daemon shared with your org by another org, or one you reach through a GPU grant, never matches. Each member links their own account, and only that member's Outreach sends use it. Nobody else in the org can send from your Telegram.
Until Venom ships its own Telegram app credentials in the release, the daemon reads them from two environment
variables, set before the first telegram login:
| Variable | What |
|---|---|
VENOM_TELEGRAM_API_ID |
the app's api_id from my.telegram.org |
VENOM_TELEGRAM_API_HASH |
the app's api_hash |
The login saves them encrypted next to the session, so a daemon that starts at login connects without them. Without them and without a saved session, the daemon never contacts Telegram.
Commands
| Command | What it does |
|---|---|
venom-daemon telegram login |
Log in (phone, code, two-step password) and print a new link code. It runs the helper (venom-telegram login) in your terminal. |
venom-daemon telegram status |
Who is logged in, today's sends and first messages against the limits, and a pause if there is one. --json for scripts. |
venom-daemon telegram logout |
Delete the session, the daemon's Telegram state and its key on this computer. |
logout does not end the session on Telegram's side. To do that too, open Telegram, Settings, Devices, and
terminate "Venom daemon". Unlinking in Settings, Comms only stops Venom Cloud from sending through it, and the session
stays on your computer until you log out.
Limits
Telegram restricts accounts that write to many strangers. The daemon enforces these limits itself, so a bug in Venom Cloud can't push your account past them:
| Limit | Value | When it is reached |
|---|---|---|
| First messages (to someone you never wrote to from this daemon) | 20 a day, by your computer's local day | the next one waits until after midnight |
| Spacing | at most one message every 30 seconds | the next one waits |
Telegram's FLOOD_WAIT |
the wait Telegram asks for | nothing is sent before it ends |
Telegram's PEER_FLOOD (too many messages to new people) |
no sends for 24 hours | that message fails with Telegram's reason, and the card in Settings shows the pause |
A message that has to wait stays scheduled and is not counted as a failed attempt. Outreach's own daily cap and send window still apply on top of these.
Use an established account, and approve every first message. A new account, or one people have reported, can be limited by Telegram even below these numbers.
When your computer is off
Venom Cloud sends to your daemon only while it is connected. When it isn't, nothing is sent: the message waits as scheduled with the note "Your computer is offline", Venom checks again every two minutes, and Outreach keeps the step due with the same note on its queue. When the daemon reconnects, the messages go out, still within the limits above.
Replies are read the same way. The daemon reports new private messages from people it wrote to, and only those. It never reads groups, channels or anyone else's messages. A reply that arrived while your computer was off is found when it reconnects, for people you wrote to in the last 30 days. A reply stops that person's Outreach sequence like a reply on any other channel.
What is stored where
| Where | What |
|---|---|
Your computer, data/telegram/ in the daemon's directory |
the session, the app credentials and the daemon's Telegram state (who it wrote to, today's counts, a pause), encrypted with AES-256-GCM, mode 0600 |
| Your computer, the key | the macOS login keychain, or the Secret Service on Linux when secret-tool is installed. Elsewhere (Windows, a Linux box without secret-tool) it is a key file, data/telegram/key, mode 0600, and the protection is your user account's file permissions |
| Venom Cloud | the account's status from the daemon's heartbeat (state, @username, today's counts, a pause, the last error, the link code's hash), and the messages and replies as Comms messages |
Malware running as your user can read the key and the session. The daemon can't defend against that. If you think your computer was compromised, end the session in Telegram's Settings, Devices.
Related
- Venom Comms providers: the other channels and how a send picks a provider.
- The desktop daemon: installing, autostart and connecting it.
- Daemon API reference: the wire contract between the daemon and Venom Cloud.