Integrations let your agents do real work inside the tools your business already uses. When an agent is connected to Gmail, it can send emails. Connected to GitHub, it can open pull requests. Connected to Google Sheets, it can read and write data.
The Integrations page shows every tool currently connected to your account — organized by who connected them — and is where you add, manage, and remove connections.
Communication channels
At the top of the page, the Communication channels section shows how your agents reach your team:
- Slack — Connect your Slack workspace to message agents in channels and DMs. Shows
Connected when your workspace is linked.
- Teams — Connect Microsoft Teams to run agents from any chat or channel.
These are your primary interfaces for working with your agents day-to-day. See Installation for setup instructions. Disconnecting a channel is admin-only.
Personal integrations
Personal integrations (Your Integrations) are scoped to you — they’re available to agents when you’re the one initiating tasks, but aren’t shared across the organization.
Each row shows:
- The tool’s logo and name
- Connection status —
Connected (active) or Pending (authorization in progress)
- For connected tools: who connected it and when (e.g., “Connected May 21, 2026 by [email protected]”)
Team integrations
Team integrations list tools connected at the organization level. These are shared — every agent can use them on behalf of any team member.
Org-wide integrations are typically set up by an admin and represent tools the whole team uses (e.g., a shared CRM, social media account, or a centralized Gmail account).
Connecting a new integration
Click Add integration in the page header to open a panel with a search field. Find the tool you want and click it to open the Connect dialog.
The dialog includes:
- Access — Choose Personal or Team. Team is only selectable by admins.
- Name — Required only when the chosen scope already has a connection to that same integration (placeholder “e.g. Marketing account”). This is how you run two connections to one tool — for example, a personal HubSpot login alongside the team’s shared HubSpot account.
- Integration-specific configuration fields and/or an API Key field, for integrations that don’t use OAuth.
- Connect and Cancel.
For OAuth integrations, clicking Connect opens an authorization popup. Once you approve access, the connection registers automatically and appears on this page.
You can also ask Violet to connect something in chat — “Connect my Gmail account” or “Add our company’s HubSpot CRM” both work, and she’ll walk you through it.
Managing a connection
Click any integration card to open its connection detail page. What you see here depends on the type of connection:
- Communication channels (Slack, Teams) show a simpler detail page — just the connection status and a Disconnect button, admin-only.
- Service integrations (everything else — your CRM, email, spreadsheets, and so on) show a fuller detail page: Status (Active, or a “Needs attention” alert if the connection has expired), Scope (Personal or Team), Auth method, who connected it and when, and an Available actions list — every action Violet can take through that connection, in a searchable list so you can quickly check whether a specific capability is available before asking for it.
Reconnecting an expired connection
If a connection’s authorization has expired, its card shows a “Needs attention” alert with a Reconnect button right on the detail page. Click it to run through the same authorization flow you used originally — once you approve access again, the connection returns to Active and any schedules or tasks that depend on it resume normally.
Removing a connection
From the ”⋯” menu, choose Delete integration. A confirmation dialog warns that deleting permanently removes the connection and revokes access; for organization-scoped connections, it carries an additional warning that this affects the whole team. Non-admins see this option disabled with the tooltip “Only admins can delete team integrations.”
Personal integrations you connect are only available for your own tasks. To make an integration available team-wide, choose Team as the access level when connecting it (admins only), or ask Violet to connect it as an organization integration.