Telegram bot

Link your Telegram account to receive notifications and create tasks straight from the bot.

If your org has the Telegram feature enabled, you can:

  • Receive any notification type as a Telegram message from our bot.
  • Create and assign tasks to teammates with a guided /newtask flow inside Telegram, no need to open the app.

Both behaviours run through the same bot account that the platform admin configures once for the whole deployment.

Linking your Telegram account

  1. Open Workspace, Profile.
  2. Find Notification Settings, Telegram.
  3. Click Link Telegram. We open Telegram in a new tab with a one-time deep link.
  4. In Telegram, tap the Start button at the bottom of the bot's chat.
  5. Come back to the profile page. It auto-detects when the bot has heard from you and flips to a green "Linked" panel showing your Telegram first name and @username.

The deep link expires 30 minutes after you click Link Telegram. If that runs out, click the button again to generate a fresh one.

If tapping Start sent only /start with no token

Some Telegram clients drop the deep-link parameter when you've already chatted with the bot before, leaving a bare /start that we can't match against your link request. The pending panel shows a fallback for this:

  1. Copy the /start <token> command from the panel.
  2. Tap open the bot in the same panel (or search for the bot in Telegram).
  3. Paste the command into the bot chat and send.

That works regardless of how Telegram handled the deep link.

Picking which events go to Telegram

After linking, the Notification Channels table grows a Telegram column. Tick the events you want delivered as Telegram messages, then click Save Preferences. The toggle is greyed out until you have a verified link.

Notifications come through as a message from the bot with a View button that deep-links back to the relevant page in Nexus ERP. Task events (assigned, submitted, approved, revision requested) ship the same field-by-field detail you'd see on WhatsApp: title, who triggered it, the org, deadline, priority, and the description or reviewer comment, all in one structured message.

The task-assigned notification carries a second button next to View: Submit task. Tapping it kicks off an in-chat submission flow without leaving Telegram, see Submitting tasks from chat.

Creating tasks from Telegram

Send /newtask to the bot. It walks you through a short flow:

  1. Pick an org if you're a member of more than one. The bot only lists orgs where you have the Create Tasks permission.
  2. Title, free text.
  3. Description, optional. Send skip to leave it blank.
  4. Assignee, the bot fuzzy-matches against name, email, or @handle.
    • 0 matches: it asks you to try again.
    • 1 match: it picks them automatically.
    • 2 or more: it shows up to six buttons, tap the right person.
  5. Deadline, free text. The parser understands the formats below.
  6. Review required? Tap Yes, review to keep the legacy flow (assignee submits, you review, the task closes when you approve) or No, auto-close to mark the task complete the moment the assignee submits. Maps to the Auto-complete on submission toggle in the web task form.
  7. Confirm, tap the green tick or the red X on the summary, which now includes a Review: line so you can double-check the choice.

When you confirm, the task is created in Nexus ERP just like one created through the workspace UI: the assignee gets the standard task-assigned notification on whatever channels they've enabled (push, WhatsApp, Telegram, in-app), and the bot sends you back a confirmation with an Open in Nexus ERP button.

Deadline formats

The deadline field accepts:

  • today or tomorrow, optionally with a time, e.g. tomorrow 5pm.
  • in N minutes / hours / days / weeks. Example: in 3 days.
  • next monday, next friday, etc. Always lands on the next occurrence in a future week.
  • ISO date, e.g. 2026-05-15. Defaults to 5pm.
  • ISO date and time, e.g. 2026-05-15 17:00 or 2026-05-15T17:00.
  • dd/mm/yyyy or mm/dd/yyyy, with or without HH:mm.

If the parser doesn't understand what you sent, it asks again. Past deadlines are rejected.

Submitting tasks from chat

The task-assigned notification has a Submit task button. Tapping it starts a short flow you can complete entirely inside Telegram:

  1. Add link? Tap Add link to paste a URL (Drive doc, GitHub PR, etc.) or Skip to submit without an attachment.
  2. Hours, only when the task awards rewards. Send a positive number, e.g. 2.5.
  3. Comment, optional. Send free text or tap Skip.
  4. Confirm with the inline buttons. The bot replies with either "submitted for review" or "marked complete", depending on whether the task creator left Auto-complete on submission on.

You can also do this from the workspace UI; the button just saves you a context switch. The submission lands in Nexus ERP exactly as if you'd used the web form.

Bot commands

CommandWhat it does
/newtaskStart the guided task-creation flow.
/cancelAbort whatever flow you're in and reset.
/myorgsList the orgs you can post tasks into from this account.
/helpShow the command list inside Telegram.

The /start command is reserved for first-time linking; you don't need to call it again after that.

Unlinking

Click Unlink in the Telegram section of your profile. This removes your verified link, disables the Telegram toggle on every notification type, and stops all delivery immediately.

Things to know

  • One Telegram account links to one Nexus user globally, not per-org. If you switch which Nexus account you use for your work, unlink and re-link.
  • Conversation state (the half-typed task) is held for 30 minutes of inactivity. After that you'll need to send /newtask again.
  • The bot can't see your private notes, only the data you send it in chat. Permissions in Nexus ERP still apply: /newtask only succeeds in orgs where you have the Create Tasks permission.
  • Unlike WhatsApp, there's no template approval involved. Notifications go through as plain styled messages from the bot.