Company integrations

Connect the office to your company's tools and manage the webhooks that post to chat channels.

The Integrations screen brings together everything that links Team Connect to other tools. This guide covers the company side: what is available, who configures it and how to manage channel webhooks.

Open Integrations

Click Integrations (the plug icon) at the bottom of the sidebar. The screen has two tabs:

Company: integrations that use the company's accounts and credentials. It shows up for people with Manage AI agents, and also for people with Manage team, because of SSO.
Mine: personal integrations each person connects with their own account. See Personal integrations.

Use Search and Category to filter. Each card shows its level (Company, Personal or Company + personal), category and status. Cards marked Planned cannot be connected yet.

Levels: who owns the integration

Level	Who sets it up	What it means
Company	People with the permission	Uses company credentials. Agents use this connection within what each agent is allowed. Someone leaving changes nothing.
Personal	Each person	Uses the person's own account. Only they connect and disconnect it; the company only sees whether it is connected, never the data.
Company + personal	Company enables, person connects	The company enables it (and, on self-hosted installs, registers the app); each person links their own account.

What is available on the Company tab

To set one up, click Configure on the card. The main ones:

LLM providers: connections to the models your agents use. See LLM connections.
Git servers: service accounts so agents can work in repositories.
Development workbench: see Workbench.
MCP servers: the way to give agents tools such as Jira, Confluence, Notion, Linear, Asana, monday.com, Sentry and HubSpot. These cards show "via MCP".
Slack and Microsoft Teams: send office channel updates to Slack or Teams and call agents from there.
Company shared drive: a Google shared drive as a knowledge base for the company's agents.
Google Calendar and Microsoft 365: on the Company tab you see whether the app is configured on the server; each person connects their own account under Mine.
SSO and provisioning (SAML, OIDC, SCIM): see SSO and SCIM.
Channel webhooks: explained below.

Some integrations depend on your plan. When a feature is not in your license, the card shows Not in plan. See License.

Channel webhooks

Webhooks let external systems, such as a deploy pipeline or a monitoring tool, post messages to a chat channel. You need the Manage webhooks permission and at least one channel.

Create a webhook

Open the chat. On the Channel webhooks card, the Open the chat button takes you there.
Click the gear icon, Configure integrations.
Fill in App name, pick the Channel, adjust Limit/min (messages per minute) and, optionally, the Description.
Click Create webhook.

Team Connect shows the webhook URL and token.

Follow deliveries

Each webhook shows its channel, status, the start of its token and the date it was last triggered. Click Deliveries to see the recent calls it received.

Rotate the token

If the token may have leaked, or as a routine security measure:

Click Rotate on the webhook.
Confirm. A new token is shown once and the old one stops working.
Update the applications that use this webhook.

Revoke

When an integration is no longer used, click Revoke and confirm. The webhook permanently stops accepting messages.

Privacy and data protection

Prefer company integrations with service accounts over someone's personal account.
Personal integration data belongs to the person: the company only sees the connection status.
Give each agent only the connections it needs. See AI agents.
Under data protection laws such as Brazil's LGPD, don't send the team's personal data to external systems without a clear purpose.