Skip to content
Changelog

Report a bug

How Connections Work

A connector is an integration Type knows how to use, such as GitHub, Google Drive, Shopify, or BigQuery. Type supports a broad catalog of integrations.

A connection is the account or credential you configure for one of those integrations.

Add the connections a department needs to its Space. Every channel in that Space can use the same setup, so you do not need to reconnect the tools for every project or workflow.

A connection can let Claude or Codex in a Space:

  • Read and write in tools such as Slack, GitHub, Linear, Notion, Google Drive, Salesforce, and HubSpot.
  • Query warehouses such as PostgreSQL, BigQuery, Supabase, Databricks, and Snowflake.
  • Use a custom API for an internal or specialized system.
  • Receive events that start Automations.
ConceptMeaning
Personal connectionUses one person’s account and its app permissions
Organization connectionUses shared workspace or company access
Global availabilityMakes a configured connection available for assignment in Type
Space accessDetermines which Spaces can use that connection
Custom APIConnects a service without a packaged Type integration

Learn how these layers fit together in Space connections.

Different connectors use different methods:

  • OAuth for delegated sign-in.
  • A customer-owned OAuth app for catalog providers that support it. Type shows the callback URL and provider settings; see Custom APIs.
  • API keys or bearer tokens.
  • Service account JSON for some organization-level Google connections.
  • No authentication when a provider does not require it.
  • Hosted MCP connections for tools that expose a Model Context Protocol server.
  • Custom API settings for your own service.

Type stores OAuth grants and encrypted API keys securely. Never paste credentials into prompts, instructions, skills, documents, or thread messages.

Google Drive & Docs uses file-level and folder-level selection instead of broad document access. Open the connection details to choose what Type may read or update and where it may create new files. If more access is needed during work, Type can show a Select files card without asking you to reconnect Google.

OAuth grants can expire or be revoked by the provider. When that happens, the connection’s card shows a Reconnect action in Space settings and in your workspace connections list, and AI can surface a reconnect card in the conversation instead of failing silently. Reconnecting repairs the existing connection in place — the Spaces that use it keep working without any re-setup.

  1. Open Space settings → Connections.
  2. Search the connector catalog.
  3. Choose an existing connection or configure a new one.
  4. Review the account and access before adding it.

You can also ask AI in a conversation to use or connect an app. Type asks before assigning an available workspace connection. If the connector has not been configured, it opens the connection flow.

A template can suggest likely connections during setup, but selecting the template does not add or authorize them.

The goal is not to replace every tool in your business. Connect the systems where your work and data already live, then let the Space use them together.

For example, a Marketing Space can combine Shopify inventory, advertising data, campaign documents, and reporting skills. A thread can use those sources to answer a question, build a dashboard, or update an app without moving the underlying systems.

  • BigQuery uses a Google Cloud service account.
  • NetSuite uses a customer-owned OAuth 2.0 integration record.
  • Shopify uses a Shopify app and its credentials.
  • Meta Ads uses a Meta system-user token.
  • Custom APIs cover tools without a packaged connector.

Connections answer, “What can AI access?” Skills answer, “How should AI handle this repeatable workflow?”

Most useful Spaces need both: the right connections and a small set of clear skills. Configure them once for the Space, then let every channel build on the same setup.