NAiOS Connectors
naios-connectorsv0.4.2Connect your services (Gmail, Slack, GitHub, Calendar, Notion…) via OAuth and use them as tools inside the chat, with prior confirmation for sensitive actions
Description
NAiOS Connectors turns hundreds of external services into tools your assistant can use directly from the chat. Connect your accounts via OAuth in a couple of clicks from the browser (no pasting tokens), and the model can act on your behalf: read and summarize emails, send emails or reply to threads, create calendar events, open issues on GitHub, post on Slack, and chain multiple actions across services in a single conversation. The tools for each connected service appear automatically in your chat and are fully gated: they only reach the model if you have the connector enabled (per-user and per-plan control). Everything is isolated per user: each person manages and executes only their own connections, and the platform key is stored encrypted at rest (AES-256-GCM). Read-only actions (search, list, read) run on the fly; actions with effects (send, delete, modify) pause and request your explicit confirmation (HITL), showing exactly what will be done and with which account, before touching anything. It supports multiple accounts for the same service (e.g. two Gmail accounts) with one active account per service, a configurable daily action quota, and optionally a per-user MCP server to plug your connectors into external clients.
Features (6)
Link Gmail, Slack, GitHub, Calendar, Notion and hundreds more with OAuth in a couple of clicks, without pasting tokens
Actions from connected services enter the assistant as tools, gated per user and per plan
Read-only actions run on the fly; sending, deleting or modifying asks for your confirmation, showing what and with which account
Connect several accounts of the same service (e.g. 2 Gmail) and choose the active account per toolkit
Each user only sees and executes their own connections; the platform API key is encrypted at rest (AES-256-GCM)
Configurable daily action limit and, if you want, a per-user MCP server for external clients
Changelog
- linkedAccount option in executeAction/proxyGet/proxyCall/stageFileForTool: a module that uses an account explicitly linked by the user (Social) is no longer blocked by that connector being silenced in the chat. The master pause still takes precedence.