Integrations and connections

Integrations is a catalog of services you can connect, and a list of what’s already connected. A service is connected once, then assigned to whichever agents need it.

Messengers

Telegram and MAX — an agent can either have a dedicated bot of its own (answers only for it, instantly), or a shared bot through a connection that routes messages to the right agent.

Telegram also has topics: an agent runs each topic of a group as its own separate conversation — see Agents for details.

Your own services

If there’s no ready-made card for a service you need, the “Generic” category covers anything else, in three ways:

• Your own service (REST API) — base address, sign-in method, a secret, and optionally an OpenAPI address. The agent calls the service itself; the secret never leaves your server.
• Incoming events (webhook) — the connection gets its own address, like /api/hooks/<token>, optionally signed with HMAC-SHA256. Every incoming event becomes a message the agent reads and can act on, the same way it would a message in a messenger. Up to 120 events a minute per connection; nothing in an event body is ever executed as a command.
• MCP server — Neo adds the server to the agent’s own toolset, without exposing secrets in the open. The agent sees new tools after a restart.

When a catalog entry is renamed or merged

Sometimes one catalog card replaces several older ones (Bitrix24, for example, offers a choice of connection method — webhook or login-and-password). Connections made under the old card move to the new one automatically, keeping their values; the fields for the method you didn’t choose are simply hidden, not required.