Useful connections.
Specific permissions.

Remote MCP for compatible agents.

Connect a client that supports remote MCP over HTTP and OAuth. Give it access to project context and the actions you select. Client compatibility varies; the connection guide explains the requirements and how to check a successful connection.

Google Drive: documents close to the work.

Authorize a registered Google account to create plain-text Google Docs, export supported connected files to PDF, and track changes to managed file metadata. Operations run as background jobs with a final success or failure status.

Provider configuration is required. In a workspace where Google access is not enabled, the app will explain that before connection.

A useful link is a good starting point.

Track an HTTPS link as a resource and attach it to projects or tasks. Registered email metadata can be matched by explicit sender or thread rules within the workspace; adding an attachment does not create a matching rule or import provider data.

A linked file needs a supported connected identity before provider operations such as export or trash are available.

Gmail: matching messages, close to the project.

Enable Gmail separately for a connected Google account, then add sender or thread rules in a project or task’s Connections panel. Matching emails are saved as references containing the subject, sender, thread ID, and Gmail link. Message bodies and attachments are not imported.

The first sync and rule changes check up to the latest 1,000 messages; later syncs follow new mail. Removing a rule stops new matches but keeps previously imported references. Gmail availability depends on the workspace’s Google connection configuration.

On the roadmap: GitHub repository sync.

GitHub connector accounts can be registered, but repository authorization and issue or pull-request sync are not implemented.

Signing in with Google or GitHub, where enabled, establishes your identity. It does not authorize a data integration.