Connect and manage your tools in Settings, then Integrations. The page shows three groups: Connected (your live connections), Available (tools you can connect right now), and Coming soon. A banner at the top of the page ("Do not see your tool?") lets you request an integration Binee does not offer yet; the request goes to the team through the help form.
Every connectable tool's card has a Details button. It opens a short overview of what Binee can do with that tool, with examples, and the exact steps to connect it. For example, a meeting tool's details explain that you can pull a meeting's action items and check whether they exist as tasks in your other connected tools.
Connections are per person
Each member connects their own accounts. Binee answers your questions through your own access: it only queries a tool through your own live connection, so you see what your account can see and nothing more. Workspace owners and admins can additionally see which tools each member has connected and whether each connection is live, so they can build automations that will actually run; that is tool names and health only, never any content from those tools. If teammates have connected a tool but you have not, Binee will tell you honestly that you need to connect your own account, and the integration card will nudge you to do so.
Cards show your own state: Connected as you means your personal connection is live. The few integrations that connect once for the whole workspace are marked as workspace-wide on their card. Both badges carry a small info button that explains the scope in plain words: Connected as you is your personal connection (Binee answers through your own access, and teammates connect their own accounts), while Workspace-wide means an admin connected it once for everyone.
Connecting and disconnecting
Connect: open Settings, then Integrations, and press Connect on the tool's card. Most tools connect by signing you in with the tool itself to grant access; Binee never sees your password. A few tools connect with a personal API key instead: the card opens a short form that shows exactly where to copy the key inside that tool, verifies the key with the tool before saving anything, and stores it encrypted.
Expiring API keys: some tools put an expiration date on their API keys. Where the tool shows that date, the connect form asks for it, and the card (and Binee in chat) reminds you before it arrives so you can generate a fresh key in the tool and press Reconnect to paste it. If a key expires before you replace it, the card says Reconnect needed and reconnecting with a fresh key fixes it in one step.
Disconnect: press Disconnect on the card. You can reconnect at any time, and disconnecting is per person: it removes only your own connection. For sign-in connections, access is revoked immediately. For API key connections, Binee deletes its stored copy of the key; the key itself stays valid in the tool, and the disconnect message tells you where to regenerate it there if you want it fully revoked.
Status badges
Badges report measured reality:
Connected: your connection is live.
Not connected: you have no connection.
A connection that dies also affects automations that run on it, including one an owner or admin built for you; the Automations page shows those automations as needing attention until you reconnect.
Status unavailable: Binee could not check the status right now. This is shown honestly instead of guessing; try again shortly, and if it persists, contact support.
Coming soon: not connectable yet.
Health details on connected cards
Some connected cards also show a row of live details:
Last synced: when Binee last refreshed its copy of that tool's data.
Sync: Syncing while a refresh is running, Up to date when the last refresh completed, Error if the last refresh failed, and Idle before the first one.
Live updates: whether the tool is pushing change events to Binee. Waiting for first activity is the normal state right after connecting: live updates start the first time something changes in the tool, and Binee reads your data either way in the meantime. Active means change events are arriving. Interrupted means the tool stopped sending events; your data still syncs on a schedule, and reconnecting restores live updates.
Details you provide yourself, like a plan tier, show Not set until you fill them in under Settings, then Workspace, in Company info.
These values report measured reality only: Active is shown because events actually arrived, never because a sync happened to run recently.
Permissions
Each connected integration has a Permissions button that opens your action permissions for it: which write operations may run without asking (Always allow) and which always ask first. You can flip operations one at a time, allow a whole section at once with its Allow all toggle (for example, every "Safe additions" operation in one click), or use the Allow all button at the top to grant everything at once; Reset all switches everything back to ask first. High risk operations always ask and cannot be set to always allow, so bulk controls never touch them.
MCP (coming soon)
Settings, then MCP is a coming-soon page for connecting AI assistants to your Binee workspace data through the Model Context Protocol, so an assistant like Claude could answer with your real projects, tasks, and insights. The one action there today is joining the waitlist: Binee emails you when access opens up. Joining the waitlist for the first time also turns on product update emails so you do not miss the announcement, and the page says so. You can turn product updates off anytime in Settings, then Notifications (the System emails section), and rejoining the waitlist never turns them back on.