NAiOS IconNAiOS Logo
Back to catalog

NAiOS Connectors

naios-connectorsv0.4.0

Connect your services (Gmail, Slack, GitHub, Calendar, Notion…) via OAuth and use them as tools within the chat, with prior confirmation for sensitive actions

ProductividadconnectorstoolsoauthintegrationsagentmcpgmailslackgithubcalendarcomposiohitlNAiOS.net Team by Netretina.Ai
Features
6
Version
0.4.0
License
MIT
Services

Description

NAiOS Connectors turns hundreds of external services into tools that your assistant can use directly from the chat. Connect your accounts via OAuth in a couple of clicks from the browser (without 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, publish on Slack, and chain multiple actions between services in a single conversation. The tools of each connected service appear in your chat automatically and are fully gated: they only reach the model if you have the connector enabled (user and plan control). Everything is isolated by 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) are executed on the fly; actions with effects (send, delete, modify) are paused and require your explicit confirmation (HITL) showing exactly what will be done and with which account, before touching anything. Supports multiple accounts of the same service (e.g., two Gmail) with one active account per service, a configurable daily action quota, and optionally an MCP server per user to plug your connectors into external clients.

Features (6)

Connect via browser (OAuth)

Link Gmail, Slack, GitHub, Calendar, Notion, and hundreds more with OAuth in a couple of clicks, without pasting tokens

Native tools in your chat

Actions from connected services enter as assistant tools, gated by user and plan

Confirmation before acting (HITL)

Read-only actions are executed on the fly; send/delete/modify requests require your confirmation showing what and with which account

Multi-account per service

Connect multiple accounts of the same service (e.g., 2 Gmail) and choose the active account per toolkit

Isolated and encrypted per user

Each user only sees and executes their own connections; the platform API key is encrypted at rest (AES-256-GCM)

Daily quota + optional MCP

Configurable limit of actions per day and, if desired, an MCP server per user for external clients

Changelog

v0.4.02026-07-26
  • Button 'My Credentials' in each service of the catalog: previously this option only appeared in services without managed OAuth, making it unreachable in Stripe (and similar). Allows connecting with your own key — e.g., a TEST sk_test_… (ticket #25)
  • New chat_max_tools setting (default 45): limit of connector tools that travel to the chat in each message. With many connected services, the prompt was triggered (~96 tools) and the model took over 120 s to start, skipping the chat cutoff (ticket #27)
v0.2.02026-06-03
  • Tool-bridge plugin→live chat: tools from connected services enter the chat (gated by user/plan)
  • Multi-turn agent loop with HITL confirmation for sensitive actions (send/delete/modify)
  • Multi-account per service: active account per toolkit + identity (email) and alias in the UI
  • Configurable daily action quota; deterministic and isolated execution by user
  • Robustness: compacting large results for the model, IPv4 output for the key allowlist, and orchestration of follow-up turns in a tool-safe model when the chat uses Gemini
v0.1.02026-06-01
  • Plugin skeleton (Phase 1)
  • Settings: NAiOS Connectors API key encrypted with secret-vault + hot-reload
  • Lazy connection engine client, tolerant of missing key/dep
  • Tool-bridge plugin→chat contract prepared (inert until Phase 3)