Connect a Telegram bot to any Friday workspace so users can chat with it over DM. Messages flow into the same conversation pipeline the web chat uses, and replies go back to Telegram.Documentation Index
Fetch the complete documentation index at: https://docs.hellofriday.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A Telegram account on your phone (the one that will own the bot).
- Friday running with the bundled tunnel active (Telegram requires a public HTTPS URL).
Setup
Create a bot with BotFather
- Open the Telegram app on your phone and search for BotFather (official account, blue checkmark). Tap Start.
- Send
/newbot. - Choose a display name (what users see, e.g. Friday Atlas).
- Choose a username ending in
bot(e.g.friday_atlas_xxxxx_bot). - BotFather replies with a bot token like
123456789:ABC-DEF-GHIJKLM.... Treat it like a password — anyone with it controls the bot.
Connect Telegram in Studio
- Open Studio and pick your workspace.
- Find the Communicators card and click Connect next to Telegram.
- Paste the Bot Token into the form, then submit.
Troubleshooting
Bot doesn't respond at all
Bot doesn't respond at all
Most likely the tunnel URL is stale (the development tunnel gets a new URL on every restart). Reconnect Telegram in Studio so it re-registers the webhook against the current tunnel.
Bot token rejected when connecting
Bot token rejected when connecting
Double-check you copied the full token from BotFather (numeric ID before the colon, secret after). Regenerate via BotFather →
/token if needed.Configure via YAML
Skip Studio and configure from disk
Skip Studio and configure from disk
For CI or fully scripted setups, paste the bot token directly into When you skip Studio, you also need to register the webhook with Telegram yourself. Grab the tunnel URL from Studio → Settings → Webhook tunnel and run:Restart Friday after editing config.
workspace.yml or the .env file in the Friday home directory (default ~/.atlas/.env).- Credentials inline
- Credentials via env
workspace.yml

