Skip to main content
Integrations connect Cogno to the tools your team already works in. Most are sources — Cogno reads their activity as events the agent learns from. GitHub is the main action — where finished work lands as a pull request. See Concepts for how sources and actions fit the loop. Open Integrations from the left nav. Services use the same compact settings rows whether connected or not: name on the left, status and action on the right.

​
How the page is laid out

GitHub’s status comes from Workspace GitHub App connections. Google Calendar shows Connected when at least one calendar account is connected. Personal GitHub sign-in is managed separately in Account → Profile → GitHub. For services that open browser authorization, choose Connect once in the list. After confirmation, Cogno opens their settings. Direct visits to an unconnected service page still offer Connect and Setup guide; longer information on connected service pages is under Details. The Microsoft Teams row reads the current connection and your unfinished setup for this Workspace: While the state is loading, the button is disabled. If loading fails, Retry checks again instead of treating the connection as absent. Starting or resuming setup requires permission to manage integrations. Teams settings shows the connected Team and tenant names. Connect and Resume start Microsoft sign-in in a popup on the web, or in the system browser when using the Cogno desktop app. When approval is needed, choose Open admin approval or Copy approval link to share it with your Microsoft tenant admin. After approval, use Select a Team to choose one Team, then Connect Team to confirm. In Channels, choose Start importing or Stop importing for each channel and review its current status. Existing tenant-wide connections retain their Event listening controls in compatibility mode until they are disconnected.
On the Free plan you can connect up to 3 integrations. Connecting a fourth shows an upgrade message instead of starting the connection — upgrade to Business to connect more. See Billing.

​
Set up an integration

These are the integrations you can connect today. Each has its own page with the connect steps.

Slack

Turn channel activity into workspace context and get task notifications as DMs.

Microsoft Teams

Bring Teams channel messages in as workspace context.

Discord

Connect servers, channels, and messages for workspace context.

ChatWork

Receive room messages and mentions for workspace context.

Messenger

Receive Facebook Page messages as workspace context.

GitHub

Import issues as tasks, sync repos and members, and track pull requests and CI.

Notion

Share selected Notion pages and databases with Cogno.

Google Calendar

Add Cogno Notetaker to supported video meetings from your calendar. Each member connects their own account.

​
Set Workspace Tool permissions

Slack and Microsoft Teams connection settings list the agent capabilities that Cogno manages. Choose Deny, Ask each time, or Always allow for each capability. This Workspace value is the security ceiling: a Project can inherit or reduce it for the same connection, but cannot increase it. Autonomous runs deny Ask each time because nobody is present to approve the action.

​
Coding agents

Integrations also lists Claude Code and Codex under Engineering. These are the coding agents Cogno runs on your machine to implement tasks — there’s nothing to connect on this page. Choosing Configure opens that coding agent’s page: an Overview of what it does on your machine, what it can do for you, and a Learn more about coding agents link.
  • In the desktop app, select Configure to jump to Settings → Machines and set that coding agent up on this computer.
  • On the web, the page is marked Desktop app feature — agent runs happen on your own machine, so the coding agent is set up from the desktop app. Get the desktop app links to the download.
See Run an agent on a task for how agent runs work and how to follow them.

​
Your connectors

Account → Connections is where you say which of your own accounts and tools Cogno may use as you — Accounts and tools Cogno may use as you. It is one answer per person, not one per project: the servers are your own credentials, so the choice follows you rather than the work. When no preference has been saved yet, connector use defaults to off. Turn on Use my connectors in Cogno runs explicitly before a run may use them. Claude Code and Codex each fold open into the MCP servers that agent reports on this computer — where each one comes from (claude.ai account, User, or Project) and its state (Connected, Needs sign-in, Failed to connect, Enabled, Disabled). Refresh re-reads them.
Reading the servers is the desktop app’s job; on the web the section says Open the desktop app to see this computer’s servers. A coding agent that is not installed, answers too slowly, or cannot list its servers says so in place of a list — Not installed, Took too long to answer, Could not list its servers.
Use my connectors in Cogno runs is what a run obeys today. The per-server Reject / Ask first / Allow choice is saved with your account, and the Engine does not gate a run on it yet.
A project’s own folder can add MCP servers on top of these; project settings lists them under Project MCP servers — see Set up a project.

​
Coming soon

The page also lists planned integrations with Coming soon and no connection action.
Vercel and PostHog have no self-serve connect flow yet, but they read a connection if your workspace already has one — their status changes from Coming soon to Connected.