Skip to content

Channels and notifications

The portal remains your main control room. A connected channel also lets you talk to the agent and receive its results from your phone.

  1. Open the agent, then the Channels tab.
  2. Open Telegram and choose Generate the Telegram QR code.
  3. Scan the QR code with your phone, or choose Open in Telegram, then tap Start in Telegram.
  4. Keep the page open: the portal checks the pairing for ten minutes and shows Connected to Telegram as soon as it succeeds.

Telegram creates a dedicated bot named after your agent. The Connected to Telegram status, followed by the bot’s name, confirms that its messages reach the right agent. The agent then restarts briefly to join Telegram. If nothing happens, choose ↻ regenerate to get a new QR code.

Do not share the QR code or the link with anyone else: the Telegram account that completes the pairing is the one the agent allows to write to it.

In Channels → Other connections, search for an app, then open its page. An owner or an administrator can enter the credentials and choose Set up the connection. Each page explains how to prepare the account or bot and which user IDs are needed.

The forms cover Discord, Slack, Mattermost, Matrix, Signal, DingTalk, Feishu/Lark, WeCom, QQ Bot, Yuanbao, Weixin, ntfy, SimpleX, IRC, Home Assistant and Photon/iMessage. Some need an external service that is already installed or an account that is already paired: the form does not create these accounts. Server addresses must be publicly reachable and use a secure transport; a server that is only reachable on your local network cannot be reached by the capsule.

Saving restarts the messaging app and may interrupt a conversation in progress. A stopped agent stays stopped. Fields that are already saved appear empty: leaving them empty keeps their value. Credentials stay inside the agent’s capsule and are never shown again.

The Applying status means the new settings are being loaded. Configured confirms that the messaging app has restarted with these settings; send a message from your app to check the connection. If it fails, refresh the page, check the credentials, then choose Save and apply. If the form was changed in another window, refresh before you continue.

The All Hermes integrations filter also shows channels that need an additional component. WhatsApp (by QR code), Teams, LINE, SMS/Twilio, BlueBubbles, WeCom Callback, Google Chat, Microsoft Graph, Buzz, Raft, Hermes Relay and A2A cannot be connected from this portal yet; their page states the missing prerequisite. The Email, Webhooks and Portal chat shortcuts open their usual settings.

Detailed steps for creating the apps are in the official Hermes messaging guide.

WhatsApp Business connects the agent to a business number through Meta’s official API. You need a Meta Business account, a Meta app with the WhatsApp product and a number dedicated to the agent. The form asks for three values: the phone number ID (Phone Number ID, a 15 to 17 digit number shown in WhatsApp → API Setup, different from the phone number), a permanent access token created for a Meta system user, and the app secret (Settings → Basic).

Then choose who the agent serves: the allowed numbers, in international format (for example +33 6 12 34 56 78), or Reply to all numbers so that it answers your customers. Other messages are ignored.

The page also shows the callback URL and the verification token specific to the agent. After saving the connection, open WhatsApp → Configuration in your Meta app, paste these two values in the Webhook section, click Verify and save, then subscribe to the messages field. Then write to the number to check the reply.

Meta only allows a free-form reply within 24 hours of the contact’s last message: a scheduled task result sent later may be refused by Meta. Only private conversations are supported.

Each member can save their Discord ID in My account → My messaging apps. In the agent’s Discord form, Choose a member adds that ID to the draft of the allowed list. You can also paste IDs: the form shows the matching names in your team, unknown IDs and ambiguous declarations. After a profile change, Refresh identities reloads the names without clearing the draft.

This link is declared by the member, without any Discord verification. It grants no rights in the portal and does not automatically link their private conversations. Permission to talk to the bot is still defined by the list saved on the agent. Changing or removing an ID in My account does not change that list. People outside your team can be allowed by entering their ID, even without a Diadems account.

Two values are required: the bot token and the IDs of the allowed users, including yours. The default channel for outgoing messages is optional. The bot’s invitation determines its server; you do not need to enter a Client Secret, a server ID or a webhook URL in Diadems.

  1. Open the Discord developer portal, create an application, then open Bot. Copy the token into the Bot token field. Reset Token creates a new one and invalidates the old one.
  2. In Bot → Privileged Gateway Intents, turn on Message Content Intent and save. The Diadems connection uses numeric IDs: Server Members Intent is not needed for this setup. Leave Require OAuth2 Code Grant off.
  3. In OAuth2 → URL Generator, choose the bot and applications.commands scopes. Grant View Channels, Send Messages, Read Message History, Embed Links and Attach Files. For threads and read receipts, add Create Public Threads, Send Messages in Threads and Add Reactions. There is no need to grant Administrator.
  4. Open the generated link to invite the bot to your server. You must be able to manage that server. Also check the bot’s permissions in the channels you want.
  5. In the Discord app, turn on User Settings → Advanced → Developer Mode. Right-click your profile, then Copy User ID. Paste it into Allowed users; separate several IDs with commas. Nicknames and mentions do not work.
  6. If you want a default destination for Hermes outgoing messages, right-click the channel, then Copy Channel ID. This field does not restrict the channels where the bot replies and does not subscribe you to portal notifications.

Save, wait for the settings to be applied, then send @your-bot Hello in a channel, or a private message to the bot, from an allowed account. By default, the bot must be mentioned in channels; a reply may open a thread. If the bot stays silent, check the token, the intent, your user ID and the channel permissions. Configured is not a substitute for this test exchange.

In Channels → Discord → Replies in channels, the Create a thread automatically setting is on by default. Turn it off so that the agent replies directly in the channel where you mention it, then choose Save and apply. Existing threads and private messages are not changed. This choice changes neither the allowed people nor the Discord permissions; the messaging app restarts to apply it.

A message is not a conversation: exchanges in the same thread share their context. Another thread has its own conversation. Without automatic thread creation, Hermes groups exchanges by channel and user by default. Conversation resets can open a new conversation. In the portal, Discord conversations with no Diadems owner are under Conversations → Members → No owner, with the Discord filter, for managers. The list of allowed Discord users does not automatically link their identity to a Diadems account.

Slack: the two tokens are not enough on their own

Section titled “Slack: the two tokens are not enough on their own”

The xoxb- token identifies the bot. The xapp- token, with the connections:write scope, enables the Socket Mode connection. You also need to:

  • grant the messaging permissions from the Hermes Slack guide;
  • subscribe to the app_mention, message.im, message.mpim, message.channels and message.groups events (the last one for private channels);
  • turn on App Home → Messages Tab and allow messages;
  • install the app in the workspace, then invite the bot to the channels;
  • copy the Slack member IDs (for example U01ABC2DEF3) of the people you allow.

After a permission change, reinstall the Slack app. After the Diadems settings have been applied, check an exchange in a private message, then in a channel.

Once connected, you can talk to the agent from Telegram. Exchanges stay organised in conversations, as in the portal.

For a scheduled task or a web trigger, choose:

  • In Diadems to find the result in Conversations;
  • On Telegram (Telegram for a webhook) to receive it directly on your phone.

The portal or the app can notify you when a reply finishes while you are not looking at it. If the right conversation is still not visible after a minute, the notification contains a preview; tapping it opens that conversation directly.

Turning this on may prompt for browser or device permission. If nothing appears, check the notification permissions in your system and browser settings.

A new notification also appears in a small card at the bottom right of the screen (at the top on a phone): the agent concerned, a two-line preview and, if you belong to several organisations, the one it comes from.

  • Open takes you straight to the conversation, mission or page concerned and marks it as read, as from the bell.
  • The cross closes the card without marking it as read: it stays in the bell.
  • The card disappears after a few seconds; it stays on screen while you hover over it or move through it with the keyboard: Alt + N (Option + N on Mac) reaches it, Esc closes it.
  • Beyond three cards, +N more opens the bell.

No card appears for the conversation you are already looking at, nor for notifications that were already there when you opened the portal or that you read on another device. In Chrome or Edge on a computer, when the page is in the foreground, the card replaces the system notification; Firefox, Safari and mobile browsers may still show both.

In My account → App & devices, you can hide the content of previews, turn on a quiet period or remove the notifications of an old device. In the Android app, the same block also lets you turn on the lock with biometrics or the phone’s code, hide the preview in recent apps and install a verified update.

For an integration under Channels → Other connections, open its page, choose Disconnect, then confirm. Its credentials are deleted and the channel is turned off for this agent. You can enter a new connection later.

The Ask [agent name] button opens a new conversation with “I’d like to know more about Channels” and the link to this guide. The request is sent once. The agent explains the prerequisites, helps prepare the settings and uses the tools available in its capsule. An account consent, a pairing or a connection managed by the portal needs your involvement. It cannot make an adapter available when its prerequisite is missing.

Never send tokens in the chat. Enter them only in the connection page or in the Vault. Each page opens a dedicated screen; the breadcrumb returns to the catalogue. Filters open a choice page. Disconnection confirmations are always shown before anything is deleted.