Telegram Channel
Telegram can be used as a fast owner channel for Tropikal. It helps owners and operators review workflow handoffs, check safe website summaries, and approve prepared changes while keeping sensitive work inside Tropikal's governed workflow, persona, and Knowledge & Capabilities model.
Telegram is not a place to paste passwords, API keys, customer exports, booking records, or private provider details.
Two Telegram paths
Tropikal supports Telegram in two product shapes:
| Path | Use it when | |---|---| | Owner channel | Owners want review notifications, handoffs, and connected website owner chat from Telegram. | | Workflow channel | A specific workflow should start from messages sent to a configured Telegram bot or chat. |
Use the owner channel for operator control. Use a workflow channel only when Telegram is part of the workflow input, such as an internal request queue or a team handoff inbox.
What you can do
With Telegram connected, an owner can:
- receive concise workflow review and handoff updates when enabled;
- open Tropikal from a notification when more detail is needed;
- choose a connected website and ask safe owner-chat questions;
- review prepared Website changes before they are published or deleted;
- approve or cancel confirmable actions with Telegram buttons.
The current owner experience is designed for quick operator decisions, not large data exports. For detailed review, use the Tropikal dashboard.
Connect your account
- Open the Tropikal Telegram bot from your workspace instructions.
- Send
/login. - Open the secure Tropikal ID link.
- Sign in with the owner account you use for Tropikal.
- Return to Telegram after the account is linked.
The bot should confirm that Telegram is connected to your Tropikal account.
If the link expires, send /login again.
If your workspace uses the first-party owner bot, the workspace instructions
may direct you to @tropikal_ai_bot. Only use the bot or setup link shown by
your Tropikal workspace.
Add Telegram to a workflow
To let Telegram start a workflow:
- Open the workflow in Tropikal.
- Open the Trigger node.
- Choose Channel.
- Click Telegram in Public Channels.
- Add the Telegram bot connection and allowed chat settings shown in the inspector.
- Save the workflow and send a test message from the allowed Telegram chat.
Treat Telegram bot tokens like passwords. Add them only in the secure setup screen, never in a chat message, workflow prompt, persona, or knowledge source.
After setup, test the workflow with a normal message, an out-of-scope message, and a message that should trigger the next action. Adjust the workflow, persona, or Knowledge & Capabilities before inviting more users.
Use website owner chat
Website owner chat lets you work with one connected website at a time.
- Send
/chat. - Choose the connected website.
- Ask a normal question, such as:
- "What content can I manage here?"
- "List the latest three posts."
- "Summarize draft pages from this week."
- Use
/donewhen you are finished.
Read-only questions should return concise summaries. If the selected website does not expose the requested content through Connected Data, sync the website or check the Website Tools setup in the dashboard.
Request changes safely
When you ask for a website change, be specific about the object and the change.
| Goal | Example message | |---|---| | Update a post | "Set post 147 live and publish it on May 24." | | Create a draft | "Create a draft research post about summer booking trends." | | Clean up content | "Find old draft posts first. Do not delete anything yet." | | Publish reviewed content | "Publish the reviewed post titled Spring Services." |
For write, publish, archive, delete, or other externally visible actions, Tropikal prepares the action and shows Confirm and Cancel buttons. The action does not run just because the chat text says "confirm." Use the buttons shown with the pending action.
If required details are missing, Telegram should ask a specific question, such as which post to update or what title to use.
Workflow notifications
Telegram can act as an owner notification channel for workflow events when it is enabled for your workspace. Typical notifications include:
- owner review requested;
- workflow run failed;
- owner handoff needed;
- important Website action awaiting review.
Notifications are short by design. They should tell you what needs attention and where to continue. Sensitive details stay in the Tropikal dashboard.
Commands
| Command | Purpose |
|---|---|
| /start | Check the bot and see suggested next actions. |
| /login | Connect Telegram to your Tropikal account. |
| /logout | Disconnect Telegram from your Tropikal account. |
| /chat | Choose a connected website and start owner chat. |
| /done | Leave website owner-chat mode. |
| /tools | See a safe list of available capabilities. |
| /personas | See safe persona summaries. |
| /workflows | See safe workflow summaries. |
| /runs | See safe recent run summaries. |
| /notifications | Check Telegram notification status. |
| /help | Show command help. |
Safety expectations
- Do not paste passwords, access tokens, provider keys, payment details, or raw customer exports into Telegram.
- Use read-only questions before asking for changes.
- Review the summary before tapping Confirm.
- Use the dashboard for detailed records, customer history, booking details, and workflow setup.
- Disconnect Telegram with
/logoutif a device is lost or an owner should no longer receive updates there.
Troubleshooting
| Symptom | First check |
|---|---|
| Login link expired | Send /login again and open the new link. |
| /chat shows no websites | Confirm the website is connected and synced in Tropikal. |
| A website action asks for more detail | Reply with the missing title, slug, ID, date, or field requested. |
| Confirm buttons are missing | Ask again with the exact Website action. Do not type "confirm" as a workaround. |
| A write action fails | Check the connected website permissions and retry from the dashboard if more context is needed. |
| Notifications are missing | Check /notifications and confirm Telegram is still connected to the right owner account. |