---
title: Connector overview
description: Call Apps connected to your OOMOL account from trusted backend code
  with the hosted Connector gateway.
lang: en
canonical_url: https://oomol.com/en/docs/connector/
markdown_url: https://oomol.com/en/docs/connector.md
---

# Connector overview

OOMOL Connector is a hosted connection service for individuals and teams. Connect Apps such as Gmail, GitHub, Notion, or Slack, then use approved actions from an Agent or trusted backend while OOMOL manages OAuth, credential storage, token refresh, and action execution.

This path uses a personal API key shaped like `api_…`. Keep the key in a backend environment or secret manager.

See [Team management](/en/docs/team-management/) when you need to invite coworkers, assign roles, or control connection access.

## Why use OOMOL Connector

- **Connect once, use it in multiple places:** Call the same App connection through oo CLI, MCP, or the SDK, and reuse it across supported Agents.
- **Reduce authentication operations:** OOMOL manages OAuth flows, credential storage, and token refresh.
- **Keep account credentials protected:** Agents, Skills, and application code use approved actions without receiving raw OAuth tokens.
- **Control access precisely:** Configure the actions allowed by each connection and the Team members who may use it.
- **Support individuals and teams:** Individuals can connect their own Apps, while teams can share connections and manage member access.

## Choose the correct Connector path

| Goal | Path |
| --- | --- |
| Call Apps connected to your OOMOL account | Hosted `Connector` client |
| Let each product user connect their own account | [SaaS integration](/en/docs/saas/) |
| Operate the runtime and credential storage yourself | [OpenConnector](/en/docs/openconnector/) |

## How a call works

1. Connect an App account in OOMOL.
2. Create a personal Connector API key in OOMOL Console.
3. Initialize `@oomol-lab/connector` in trusted backend code.
4. Select an action and, when needed, a named connection.
5. Connector calls the provider and returns the action result.

Your backend receives action results and execution metadata without reading the provider's raw OAuth token.

## SDK capabilities

| Need | SDK surface |
| --- | --- |
| Execute a modeled operation | `execute` or `executeRaw` |
| Call an endpoint without a modeled action | `proxy` |
| Discover providers and action schemas | `catalog` |
| List connected accounts | `apps.list` |

## Start building

Follow [Call connected Apps with the SDK](/en/docs/connector-client/) to install the package, create an API key, make the first call, and select a connection. Use the [TypeScript SDK reference](/en/docs/connector-sdk/) for shared configuration, error handling, and the complete API surface.

## Keep the key on the backend

Do not include a personal API key in browser bundles, public repositories, prompts, or client-side logs. Use a Connector SaaS project when requests must be scoped to individual product users; do not share one personal key across unrelated end users.