Connectors

• —A connector links an outside app to the assistant, so it can look things up there and act there. Slack, Notion, Google Drive, HubSpot and about a thousand more can be connected. "Find the proposal in Drive and tell me what it says about pricing." "Post this update in the sales channel." Connectors live under Connectors in the sidebar.
• —To connect an app, pick it from the list, choose who it is for and what the assistant may do, then finish on the app’s own sign-in page, or paste a key from the app there. The password or key never passes through OpenEmail’s chat, its API or the assistant. The connector is pending until you have finished, and active after that.
• —A connector is for you alone or for the whole workspace, and the assistant may either only look things up through it or also make changes. You can change that later, and pause a connector and resume it. Disconnecting gives up the access in the outside app too. If the app stops accepting the connection, the connector asks to be reconnected, and a fresh link brings it back as the same connector.
• —In a chat the assistant sees what is connected, finds the right action in the app and reads straight away. For anything that changes something in the app, such as sending a message, creating or updating a record or deleting, it shows a card for you to approve first, even when you asked for it directly. A connector that only looks things up refuses changes, and what an app returns is treated as information, never as instructions.
• —A task uses connectors only when Connectors is turned on under its Extra tools, and only the ones connected for the workspace, never one that belongs to a single person. It reads alone. Every change in an app waits under Needs you, whatever the task may otherwise do alone, and a task that uses connectors never replies to mail by itself: every reply waits for your approval.
• —Every call made through a connector is recorded for 90 days: when, which app and which action, whether it read or changed something, whether it worked, and whether it came from a chat, a task, the API or an agent. What was sent to the app and what came back are never kept by OpenEmail.
• —Three permissions decide who does what: one to see connectors and what was done through them, one to have the assistant use them, and one to connect, pause and disconnect apps and set what the assistant may do. Owners and admins hold all three, Member holds the first two and Viewer the first. Whoever may connect an app may connect it for themselves or for the workspace.
• —A plan holds 2 connectors on Free, 10 on Starter and 50 on Business for an account, and as many again for a workspace. Enterprise sets no limit of its own, and nothing holds more than 200. When a workspace moves to a smaller plan, the newest connectors beyond the limit are paused, not removed.
• —Connections are held by an outside provider, which also keeps a record of what the assistant sends to an app and what the app answers, for up to a year. The Privacy page lists it.
• —Connectors are on the REST API under /connectors, /connector-apps, /connector-categories and /connector-calls, in every SDK as connectors, on the command line as openemail connectors, and on the MCP server. Over the API a change runs at once with nobody asked, so the caller decides. Three webhook events tell your systems when a workspace connector is connected, is disconnected or needs reconnecting.

Connecting takes a minute, and the sign-in happens on the page of the app itself.

1. 1Open Connectors in the sidebar and find the app under Browse, by its name or by a category.
2. 2Choose who the connector is for: only you, or the whole workspace.
3. 3Choose what the assistant may do through it: only look things up, or also make changes.
4. 4Finish on the sign-in page of the app, or paste a key from the app there. The connector is pending until you have finished, and active after that.

• —Your password or key for the app never passes through OpenEmail’s chat, its API or the assistant.
• —When an app stops accepting the connection, the connector says it needs reconnecting. A fresh link brings it back as the same connector, so the tasks that use it carry on.
• —Pause a connector to stop the assistant from using it, and resume it when you want it back.
• —Disconnecting removes the connector and gives up the access it held in the outside app too.
• —Connectors can be switched off for the whole service. The page is then hidden.

• —Owners and admins hold all three. The built-in Member role holds connectors:read and connectors:use, and Viewer holds connectors:read.
• —The same permission covers both kinds of connector: whoever may connect an app may connect it for themselves or for the workspace.

Connectors are in the REST API under /connectors, /connector-apps, /connector-categories and /connector-calls, in every SDK and in the CLI under connectors, and in the MCP tools, which the assistant uses as well.