Adapter

Adapter vs. connector

Adapters are built into agent-hub for Telegram, Discord, Slack, and Webhook. If your chat platform isn’t in that list, try the Connector page instead — if the platform has a long-polling bot API, you can connect it with no code required.

What an adapter takes care of

• Incoming messages — every message from the platform is turned into a common shape regardless of platform: who sent it, where (chat / topic / thread), the content, whether it’s a reply to an agent’s message, and any attachments.
• Platform capabilities — each platform declares what it supports (threads, buttons, reactions, editing messages, typing indicators…). The core fills in for whatever the platform doesn’t support — for example, showing choices as a numbered list when the platform has no buttons. An adapter never fakes a capability it doesn’t have.
• Sending messages — always returns one of three states: delivered; definitely not delivered (retried once in plain form); or uncertain (never retried, to avoid sending a duplicate).

When no adapter is usable

If no adapter can be selected (misconfigured or the platform is unavailable), you’ll see:

FATAL: no usable gateway adapter (active gateway: telegram)

Exactly one adapter runs at a time — the active adapter comes from the current gateway configuration (the gateway enabled on the Integrations page), never from an environment variable.