> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corebasehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SaaS connectors

> Connect a SaaS app and your agents can use it — take actions and search its content, with the same governance as any other source.

Connect an app like Jira, Gmail, GitHub, or Notion and it becomes a source your agents can use. You don't write an integration per app: click connect, authorize, and the app is live — your agents can act in it and search its content, governed exactly like everything else.

## Connect an app

In **Panel → Sources → Add integration**, native sources (Microsoft 365) and SaaS apps appear in one unified grid. Pick an app, complete the OAuth flow, and it's connected — tools enabled by default.

Authentication runs through a **managed OAuth layer**: the OAuth tokens live there, not in CoreBase, and calls go through an authenticated proxy that injects and refreshes them. To your agents, a connected app behaves like any other API source.

<Note>
  SaaS connectors are a **cloud-relay** tier — auth and proxied calls pass through the connector cloud. For on-prem databases, the **sovereign** path via [CoreMCP](/coremcp/intro) keeps data on your own network. Pick the tier your compliance needs.
</Note>

<Note>
  Connecting here creates **one shared account for the whole org** — every chat and every agent uses it. Embedding the widget for external end-users and want each visitor to link their *own* Gmail/Jira/etc. instead? See [Connected accounts](/platform/widget#connected-accounts).
</Note>

## Available connectors

50+ apps across the categories below, with more added regularly. Browse the full grid at [corebasehq.com/integrations](https://corebasehq.com/integrations).

| Category          | Apps                                                           |
| ----------------- | -------------------------------------------------------------- |
| **Dev tools**     | GitHub, GitLab, Bitbucket, Jira, Linear, Asana, Trello, Sentry |
| **Communication** | Slack, Microsoft Teams, Gmail, Outlook, Discord, Zoom          |
| **CRM**           | Salesforce, HubSpot, Pipedrive, Zoho                           |
| **Support**       | Zendesk, Intercom, Freshworks                                  |
| **Knowledge**     | Notion, Confluence, Google Drive, Dropbox, Box, Airtable       |
| **Payments**      | Stripe, PayPal, Square, QuickBooks, Xero                       |
| **Marketing**     | Mailchimp, Klaviyo, SendGrid, Mailgun                          |
| **Commerce**      | Shopify, WooCommerce, BigCommerce                              |
| **Productivity**  | Google Calendar, Calendly, Google Sheets, Todoist, ClickUp     |
| **Analytics**     | Google Analytics, Mixpanel, Amplitude                          |

## Take action in any app

Every connected app can act, not just feed search:

* **Typed tools** — when the provider ships an OpenAPI spec, each operation becomes a precise, typed tool.
* **Generic request tool** — when it doesn't, CoreBase exposes a single governed `request` tool: the agent provides a method and path, and the call goes through the authenticated proxy.

Either way the agent does real work — open a Jira issue, send a Gmail draft, post to a channel — subject to governance.

## Search an app's content

Connected apps also feed **retrieval**. Turn it on per connection and the app's content syncs into [Unified Context](/concepts/corporate-memory), incrementally and in the background — no manual exports. From then on an agent can search across the app's messages, issues, docs, and records, with citations. Actions and retrieval are both live today.

## Governance carries over

Connectors inherit the same controls as any source — read-only by default, source-scoped, per-tenant isolated, and audited. The generic `request` tool exposes only `GET` until you enable writes, and mutating operations are never handed to an agent on a read-only connection. See [Governance](/concepts/governance) for the full model.

## Automate on app events

Want something to happen when a Jira issue lands or a Stripe payment comes in? Let your workflow tool own the trigger — n8n, Zapier, and Make all listen to those apps natively — and have the workflow call the [OpenAI-compatible chat endpoint](/api-reference/endpoints/chat) with `stream: false`. One HTTP step returns the full governed answer as JSON, ready to route to Slack, email, or your own systems.

## Next

<CardGroup cols={2}>
  <Card title="Ask across your apps" icon="robot" href="/quickstart">
    Put your connected sources to work in chat, the API, or the widget.
  </Card>

  <Card title="Call it from a workflow" icon="bolt" href="/api-reference/endpoints/chat">
    One `stream: false` HTTP call from n8n, Zapier, or cron.
  </Card>
</CardGroup>