Skip to main content

Bring your tools into Chief

Integrations let Chief read from and act in the apps you already use — including Google Drive, Gmail, Google Calendar, Notion, and Slack. Once connected, Chief can pull that data into a task, search it, and, for some tools, take actions on your behalf.

What you can connect

  • Google Drive — search your Drive, read files, and create or edit documents from a task.
  • Gmail — read, search, draft, send, label, and archive email.
  • Google Calendar — read your calendars and events, create or update events, and send RSVPs.
  • Notion — sync the pages and databases you pick into a Project and work in Notion from a task.
  • Slack — search messages and read channels using your own Slack access.
  • Linear — index a team’s issues into a Project and create or edit issues from a task.
  • GitHub — index issues, pull requests, and discussions from chosen repositories and work on them from a task.
  • Custom Integrations by MCP Servers — connect remote tools to the organization, deploy them to Projects, and let each member authorize their own account when the server uses per-user OAuth.
  • Chief’s hosted MCP server — let Claude Code, Cursor, and other MCP clients work with your Chief Project.
Organizations on a qualifying plan can also set up Google Workspace once for the whole org, so Gmail, Calendar, and Drive work across users without each person connecting their own account — and Drive files can sync into a Project’s knowledge. See the Google Workspace admin guide for that.

Where to connect them

It depends on whether the connection belongs to your organization or to you:
  • Organization-level tools — Google Workspace, Slack, Notion, Linear, GitHub, and custom integrations — are connected once by an organization owner under Organization › Integrations, then deployed to Projects. Only owners see the connection controls there.
  • Your own Slack account — once an owner has deployed a Slack workspace to a Project you’re in, open Settings › Connected accounts and click Connect Slack next to the workspace. From a task, open Tools & integrations, find Slack under Connected, and click Connect.
  • Your own Google account — connect from a task: when Chief needs Gmail, Calendar, or Drive access it hasn’t got, it shows a Connect Google card. You can also open Tools & integrations and use Connect beside Google under Needs your connection. If your organization has Google Workspace calendar scheduling available, Settings › Connected accounts also shows a Google Calendar card where you can choose whether Chief schedules Live Sessions for your calendar meetings.

Actions and asking first

When an integration can change something — sending an email, creating a calendar event, moving messages to Trash — Chief shows you a confirmation card and waits for your Approve before it runs. Eligible write actions also offer Always allow, which approves the current action and saves that operation for later. You can review these permissions in Settings › Tool permissions or manage them from Tools & integrations. See Managing integration permissions & connection status for details.

Build another connection

Chief has a REST API, a vendor-hosted MCP server, and a command-line client for building other connections — see Build on Chief.

FAQ

No. Connect only the tools you want Chief to use. Each one is independent, and you can disconnect any of them later.
Most connections are shared. Google Workspace, Slack workspaces, Notion, Linear, GitHub, and custom integrations are connected once by an organization owner and deployed to Projects. A personal Google connection, your own Slack account link, and your connection to a custom integration that uses per-user OAuth are tied to your account.