Connectors give your AI colleagues governed access to the systems your organisation already runs on. An agent filling a role can read the mail, calendars, documents, tickets and ledgers that role is responsible for, without anyone handing it a password.
Nobody shares a credential with an agent. Admins decide which data sources exist and how broadly they may be owned. Governance decides which roles get them. Credentials are held in an external vault, never travel to the agent, and every use is recorded against the role that made it. That is the difference between enterprise-grade third-party access and an API key pasted into a prompt.
Nestr ships ready-made connectors for the tools most organisations already use. Adding one is a matter of picking a tile: the endpoint, the transport, the authentication method and the OAuth client come with it.
Google Workspace: Gmail, Drive, Calendar, Docs, Sheets, Tasks, Analytics and Search Console.
Microsoft 365: Outlook Mail, Outlook Calendar, OneDrive and Teams.
Work management and engineering: Slack, GitHub, GitLab, Jira and Confluence, Linear, Asana, Monday.com, ClickUp, Notion and Sentry.
Finance, sales and support: Stripe, Xero, QuickBooks, Moneybird, HubSpot and Intercom.
Files and automation: Dropbox, Box, Zapier and Make.
The catalogue is a convenience, not a boundary. Register a custom connector against any HTTP API or any Model Context Protocol server your organisation runs, including internal systems that will never appear in anyone's catalogue. A custom connector carries exactly the same governance as a ready-made one.
A connector is normally bound to a role's domain. Whoever fills that role reaches it, human or agent, and someone leaving the role loses that access as a consequence of governance rather than as a chore somebody has to remember. Connectors can also be held by the workspace, by an individual, or by a named agent.
Exposure is re-checked every time a credential is handed out, so switching a connector off stops it flowing through the bindings already made, not merely blocking new ones.
A connector can require a person to approve before an agent acts: nothing, writes only, or everything, plus named operations that always need a person. When an agent reaches a gated action it pauses and asks in the conversation, and proceeds only on an answer.
You do not have to work through settings screens. Ask Nestradamus to connect a tool for a role and it will find the right template, register the connector, bind it, and hand you the link to sign in with, all within the permissions you already hold.
.png){kind=logo}
