Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.raziel.fun/llms.txt

Use this file to discover all available pages before exploring further.

Integrations connect your team to external services so agents can receive messages, push code, and deploy projects. Each token you provide is validated against the upstream API, encrypted at rest, and pushed into the VM environment only for the running process.
You can add or update integrations at any time from the team dashboard. Navigate to your team and open the Integrations tab.

​
Telegram

Your team replies in any conversation the bot is part of. Whitelist specific Telegram user IDs to control who can send messages.
1

Create a bot

Open Telegram and message @BotFather. Use /newbot to create a bot and copy the token it gives you.
2

Paste the token

In the dashboard, open your team → Integrations → Telegram. Paste the bot token.
3

Whitelist users

Enter the Telegram user IDs of accounts allowed to message the bot. Find a user ID by forwarding their message to @userinfobot. Separate multiple IDs with commas.
4

Save

Click Connect. Raziel validates the token against Telegram’s API, registers a webhook, and marks the integration as connected.

​
Discord

Your team replies in any channel the bot is invited to. Whitelist Discord user IDs to restrict who can trigger responses.
1

Create a Discord application

Go to the Discord Developer Portal and create a new application. Under Bot, add a bot user and copy the token.
2

Invite the bot to your server

Under OAuth2 → URL Generator, select the bot scope and the permissions your agent needs (at minimum: Send Messages, Read Message History). Open the generated URL to invite the bot.
3

Paste the token and whitelist

In the dashboard, open your team → Integrations → Discord. Paste the bot token and enter the Discord user IDs to whitelist.
4

Save

Click Connect. Raziel validates the token, pushes it into the VM environment, and marks the integration as connected.

​
GitHub

Your GitHub Personal Access Token is stored via gh auth login inside the VM. Every shell session and agent process sees the credential without any extra environment wrangling.
1

Generate a PAT

Go to github.com/settings/tokens and generate a Personal Access Token with the scopes your agent needs (typically repo, read:user). Fine-grained tokens work.
2

Paste the token

In the dashboard, open your team → Integrations → GitHub. Paste the token.
3

Save

Click Connect. Raziel validates the token, configures gh authentication inside the VM, and marks the integration as connected.
Once connected, your agent can clone, push, and open pull requests using gh or git without any additional setup.

​
Vercel

Your Vercel token is stored via vercel login inside the VM. The vercel deploy command works without setting the VERCEL_TOKEN environment variable.
1

Generate a Vercel token

Go to vercel.com/account/tokens and create a new token. Give it a descriptive name like raziel-team.
2

Paste the token

In the dashboard, open your team → Integrations → Vercel. Paste the token.
3

Save

Click Connect. Raziel validates the token, runs vercel login --token <token> inside the VM, and marks the integration as connected.

​
Token security

All integration tokens are encrypted before being stored. Plaintext credentials are injected into the VM environment only for the running process — they are not persisted in plaintext.
Raziel does not persist plaintext tokens in the database. If you rotate a token upstream, update it in the dashboard to push the new value into the VM.