Obvious/Help Center

Integrations Overview

Published February 27, 2026 · Last updated March 7, 2026 · 4 min read

Integrations connect Obvious to the tools your team already uses — Slack, Google Calendar, Gmail, Outlook, GitHub, and dozens of other services. Once connected, your agent can read messages, send emails, check calendars, and interact with external platforms directly from your project.

What Integrations Do

A connected integration gives your agent access to an external service. Instead of switching between apps, you work through Obvious: ask the agent to check your calendar, send a Slack message, search your email, or pull data from a connected CRM. The agent handles the API calls, authentication, and data formatting behind the scenes.

Integrations fall into a few categories based on what they connect to.

Communication

Connect Slack, Microsoft Teams, Discord, or other messaging platforms. Your agent can read channel messages, send messages, reply to threads, and add reactions. For email, connect Gmail or Outlook to search, read, compose, and send messages directly through the agent.

Calendar

Connect Google Calendar, Outlook Calendar, or Apple Calendar. Your agent can list upcoming events, create new meetings, update event details, and check availability — useful for scheduling workflows or generating daily agenda summaries.

Development

Connect GitHub to give your agent access to repositories, pull requests, issues, and code. This is particularly useful for teams that want to bridge project management in Obvious with development workflows on GitHub.

Data and CRM

Connect services like your CRM, accounting tools, or commerce platforms through the integration catalog. Your agent can query customer records, pipeline data, invoices, and other business data, then bring it into your Obvious workbooks for analysis.

Connecting a Service

Integrations are managed at the workspace level, which means a connection made by one team member is available to all projects in that workspace.

To browse available integrations, open Settings from the left sidebar, then select Workspace, then Connectors. The connector catalog shows every available service, organized by category. Each connector card shows the service name, a brief description, and whether it's already connected.

Clicking a connector opens the setup flow. Most integrations use OAuth — you sign in to the external service, authorize Obvious, and the connection is live. Some services require an API key or other credentials, which you enter during setup.

Once connected, the integration appears in your list of active connectors with a status indicator showing whether the connection is healthy.

Using Integrations in Chat

Connected integrations work through your agent. You don't interact with them through a separate UI — you ask the agent to do things with them.

Check my calendar for next week and list any meetings with external participants

Send a message in the #product-updates Slack channel: "Q1 report is ready for review"

Search my email for messages from acme@example.com in the last 30 days

Pull the latest pipeline data from our CRM and add it to the Pipeline sheet

The agent knows which integrations are connected and uses them automatically when your request involves an external service. If a service isn't connected yet, the agent tells you what's needed and how to set it up.

Managing Connections

Each connected service shows its status in the Connectors settings page. You can disconnect a service at any time, which revokes access and removes the credentials. Reconnecting follows the same setup flow as the initial connection.

If a connection breaks — typically because a token expired or permissions changed — the status indicator reflects the issue. Reconnecting usually resolves it by re-authorizing through OAuth.

Some integrations support multiple connections to the same service. For example, you might connect both a personal and a work Google Calendar, or multiple Slack workspaces. Each connection appears separately in your connector list.

Secrets and API Keys

For services that don't use OAuth, Obvious stores credentials as secrets. Secrets are encrypted and scoped to your project, team, or workspace depending on how they're configured. Your agent can request secrets during a conversation when it needs credentials to access a service — you provide the key once, and it's stored securely for future use.

Secrets are available to your agent as environment variables, which means they work in both conversational requests and automated tasks. You never need to paste API keys into individual messages.

Next Steps

Was this helpful?