LangBot
Power LangBot chat bots for Telegram, Discord, Slack, Feishu and more with RuToken models.
LangBot is an open-source platform for building instant-messaging bots. It connects to Feishu, DingTalk, WeChat, QQ, Telegram, Discord, Slack and other platforms and supports knowledge bases, agents and MCP. Docs: docs.langbot.app, source: GitHub.
Prerequisites
- An API key: open the console, go to API Keys and create a dedicated key (for example, named
LangBot). - A running LangBot instance — see the official deployment docs.
Configuration
1. Add a chat model
-
In the LangBot web UI, open Models and add a new model.
-
Choose an OpenAI-compatible requester (LangBot also lists a dedicated New API requester for this kind of gateway) and fill in:
Field Value Model name a model ID from the Model Square, e.g. gpt-4o-miniBase URL https://rutoken.ai/v1API Key sk-xxxx -
Save the model.
If both LangBot and the gateway run in Docker on the same machine, localhost inside the LangBot container is not the gateway. Use the public address https://rutoken.ai or follow LangBot's container network guide.
2. Use it in a pipeline
Open Pipelines, select the model you just added for the pipeline's AI settings and save. Bind the pipeline to a bot — see Deploying Bots for each messaging platform.
3. Optional: knowledge base embeddings
RuToken also provides embedding models. Add an embedding model in LangBot with the same Base URL and key (for example text-embedding-3-small), then select it when creating a knowledge base.
Verify
Use Debug chat in the pipeline, or message a bot bound to the pipeline. A reply means the model works; the request appears in the console under Usage Logs.
Troubleshooting
| Symptom | Fix |
|---|---|
401 / invalid API key |
Copy the full key again; check that it is enabled, not expired and has quota left. |
404 / not found |
The Base URL must end with /v1. |
| Model not found | The model name must exactly match an ID in the Model Square and be allowed for the key. |
| Connection refused / timeout | The LangBot container cannot reach the gateway address — see the network note above. |