Setup & Connection
The Telegram integration takes under two minutes to connect. No developer configuration or webhook setup is required.
Open Integration Settings
In your Everia project, go to Settings → Integrations → Telegram and click Connect.
Start a chat with the Everia bot
A link to the bot opens automatically. Click Start in Telegram to initiate the conversation.
Authorize the bot
Send the one-time authorization code shown in Everia to the bot. This links your Telegram account to your Everia workspace.
Link the project
Send /link in the bot chat. If you belong to multiple Everia projects, you will be prompted to select one. The bot is now connected to that project.
Using in a group chat
- Add the Everia bot to a Telegram group and run /link to associate the group with a project.
- All members of the group can then use bot commands — their actions are attributed to their linked Everia account.
- Notifications sent to the group are visible to all members.
/unlink and then /link again.Bot Commands
Send /help to the bot at any time to see the full command list. Here are all supported commands:
/create [title]— Create a new ticket with the given title in the linked project/status [ticket-id]— Get the current status, assignee, and sprint for a ticket/assign [ticket-id] [user]— Assign a ticket to a team member by name or email/close [ticket-id]— Mark a ticket as Done/sprint— Show the active sprint — name, dates, completion %, blockers/sprint list— List all sprints (active and recent)/search [query]— Search KnowHub and return matching page excerpts/ask [question]— Ask the AI a question about your project — answers are grounded in your data/link— Link this chat to an Everia project/unlink— Remove the link between this chat and its project/help— Show all commandsCreating tickets from messages
You can also forward or reply to any Telegram message and choose Create Everia Ticket from the bot's quick-action menu. The message content becomes the ticket description automatically.
/create [P1] Payment gateway timeout on checkoutNotifications
Configure which events trigger Telegram messages. Go to Settings → Integrations → Telegram → Notification Settings.
Test run completed
Summary of pass / fail / blocked counts with a link to the report.
Test run failed threshold
Alert when the fail rate exceeds a configurable percentage.
Ticket assigned to me
Personal notification when a ticket is assigned to your account.
Ticket status changed
Notify the channel when a ticket moves to a new status.
Sprint started / closed
Announce when a sprint kicks off or wraps up.
Blocker added
Immediate alert when a ticket is marked as Blocked.
AI Features
The Everia bot includes an AI assistant that can answer questions about your project in natural language. It uses your KnowHub content, ticket data, and sprint history as context — it does not fabricate answers from general knowledge.
Asking questions
- Use /ask followed by a plain-English question: /ask What tests are failing in the current sprint?
- The bot searches your project data and returns a concise, cited answer.
- Answers include links back to the relevant tickets, pages, or test runs so you can dive deeper.
KnowHub search
- Use /search to find documentation pages by keyword.
- The bot returns a snippet from the most relevant pages and a direct link to each.
- Results are ranked by relevance, not recency — the most applicable page appears first.
Troubleshooting
Bot does not respond to commands
Check that the bot is still a member of the group and that the Telegram integration is enabled in Everia Settings → Integrations. Reconnect if the token has expired.
/link shows 'No project found'
Ensure you are logged in to an Everia account with at least Member access to at least one project. Open the web app and confirm you can see the project.
Notifications are not arriving
Check Settings → Integrations → Telegram → Notification Settings and confirm the relevant event types are toggled on. Also check that Telegram has not muted the bot.
Ticket created with wrong project
Run /unlink and then /link again to re-select the correct project. All subsequent commands will target the newly linked project.