Plugins
A plugin gives bots tools from another service: search the web, read a Notion page, update a deal in your CRM. Plugins are installed once for the workspace, from the catalogue.
The catalogue
Section titled “The catalogue”| Category | Plugins |
|---|---|
| CRM | amoCRM, Bitrix24 |
| Support | HelpDeskEddy |
| ERP | МойСклад |
| Productivity | Notion, Asana, Planfix, Яндекс Вики |
| Developer | GitHub, Linear |
| Web search | Firecrawl, Tavily, Exa, Parallel |
Some connect with an API key you paste in; others sign you in with the service (OAuth).
Who can use it
Section titled “Who can use it”When you install a plugin you choose who it is for:
- Every bot — any bot in the workspace (default).
- Chosen bots — only the bots you pick.
- Only me — only your own conversations. The credential is yours; a colleague’s thread never uses it.
When the bot asks first
Section titled “When the bot asks first”Each installation has an approval setting for what happens when a bot reaches for one of its tools:
| Setting | Behaviour |
|---|---|
| Always allow | The bot just uses it |
| Ask before it changes anything | Reading runs freely; anything that writes waits for you |
| Ask the first time | Each tool waits for you once, then it is allowed |
| Ask every time | Every call waits for you |
When a call waits, the conversation shows an approval card and the run pauses until you answer. A tool that isn’t declared as read-only counts as a change.
Something not in the catalogue?
Section titled “Something not in the catalogue?”For a service with an HTTP API, add an HTTP tool.