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

# Integrations

> Connect Google Sheets, Google Drive, Gmail, Outlook, password vaults and MCP clients to Skyvern, and run your agents from Zapier, Make, n8n or Workato.

Open **Integrations** in the sidebar to connect outside services to your agents. The page lists everything you have connected at the top, then every integration you can add under **Available**. Search by name, or filter with the category chips (**Workspace**, **Communication**, **Docs**, **Agent Orchestrators**, **Credentials**).

![Integrations page with the search box, category filters, connected Google Sheets and Gmail cards, and the Available grid](https://mintcdn.com/skyvern/amcBKP0IBwdNswdN/images/cloud/cloud-integrations-page.png?fit=max\&auto=format\&n=amcBKP0IBwdNswdN\&q=85\&s=fae702df4b4fa9c883c9172a6e3871dc)

Every integration with a **Connect**, **Configure** or **Set up →** button is self-serve: you connect it yourself, with no sales call. The sidebar's **Integrations** group also has shortcuts to **API keys**, **MCP**, **1Password** and **n8n**.

| Integration | Category | What it does | Button |
| - | - | - | - |
| Google Sheets | Workspace | Read and write sheets in your agents | **Connect** |
| Google Drive | Workspace | Upload run files to Drive folders | **Connect** |
| Gmail | Communication | Read verification codes and send email from your agents | **Connect** |
| Outlook | Communication | Find verification codes and emails in your inbox | **Connect** |
| 1Password | Credentials | Use logins from your 1Password vaults | **Configure** |
| Bitwarden | Credentials | Use logins from your Bitwarden vault | **Configure** |
| Azure Key Vault | Credentials | Read secrets from Azure Key Vault | **Configure** |
| Custom Credential Service | Credentials | Fetch credentials from your own HTTP API | **Configure** |
| MCP | Agent Orchestrators | Connect Claude, Cursor, Codex and other AI clients | **Set up →** |
| n8n, Zapier, Make, Workato | Agent Orchestrators | Run Skyvern agents from those platforms | **Learn more** |
| Google Docs, Notion | Workspace, Docs | Not available yet | **Request →** |

Don't see what you need? Click **Request →** on the **Request another integration** card and name the service.

## Google and Microsoft accounts

Google Sheets, Google Drive, Gmail and Outlook connect through Google or Microsoft sign-in.

**1. Click Connect**

Click **Connect** on the tile.

**2. Name the connection**

Enter a name, such as "Finance Gmail". You pick the account by this name in your agent's blocks. For Gmail, choose what agents may do: **Read inbox** (on by default) and **Send email**. Click **Continue to Google** (or **Continue to Microsoft** for Outlook).

**3. Approve access**

Sign in and approve every permission on the consent screen. Skyvern sends you back to Integrations, where the account appears under **Connected**.

What each connection asks for, and where you use it:

| Integration | Access requested | Where you use it |
| - | - | - |
| Google Sheets | Read and write spreadsheets, read Drive file metadata | **Google Sheets Read** and **Google Sheets Write** blocks |
| Google Drive | Full Drive access | **Cloud Storage** block with storage type **Google Drive**; **File Download** block for Drive links |
| Gmail | **Read inbox**: read-only mail. **Send email**: send mail as the account. | **Email Inbox** block and email-based 2FA on [credentials](https://skyvern.com/docs/credentials.md) (read); **Send Email** block with **Send with** set to the account (send) |
| Outlook | Read mail (`Mail.Read`) | **Email Inbox** block, and email-based 2FA on [credentials](https://skyvern.com/docs/credentials.md) |

Block settings are in the [blocks reference](https://skyvern.com/docs/reference/blocks.md).

### Manage a connected account

Each connected card lists its accounts. From there you can:

* **Add another account**: click **Add another Gmail account** (or the matching name) to connect a second inbox or Google account.
* **Rename** or **Disconnect**: open the **...** menu on the account row. The name you set is what agent blocks show in their account picker.
* **Turn on reading or sending** (Gmail): the account row shows **Read inbox** and **Send email**. Click the one that isn't on yet and approve the extra permission. Sending needs the account's address, so an older connection may ask you to reconnect first.
* **Reconnect** (Google only): if the card shows **Needs reconnect**, the authorization expired or you didn't approve every permission. Click **Reconnect** and approve again. Agents that use the account resume without edits.

> [!WARNING]
>
> Disconnecting cannot be undone. Agents that use the account fail on their next run until you reconnect it or pick another account in their blocks.

## Password vaults

The four **Credentials** tiles let agents log in with secrets you already keep elsewhere. Click **Configure**, fill in the form, and save. The tile then shows **Status: Active**, or **Status: Inactive** if Skyvern could not use what you entered.

| Vault | What you enter |
| - | - |
| 1Password | **Service Account Token** (starts with `ops_`). The dialog walks you through creating one. |
| Bitwarden | **Email** and **Master Password** of the Bitwarden account. |
| Azure Key Vault | **Tenant ID**, **Client ID** and **Client Secret** of an app registration that can read the vault. |
| Custom Credential Service | **API Base URL** and **API Token** of your service. Click **Test Connection** before you save. |

For Bitwarden, **Email** and **Master Password** are the default. Add a **Personal API key** if Bitwarden asks Skyvern for a verification code (a new-device check or two-step login). Skyvern cannot enter these codes. Without a key, the run stops with a message that explains this.

In the Bitwarden web app, open **Settings > Security > Keys > View API key**. Copy `client_id` (starts with `user.`) and `client_secret` into the form. Organization API keys do not work.

The key plus your master password open the vault without a code or two-step check. Store and share the key like your master password.

To rotate the key, select **Rotate API key** in Bitwarden, then save the new secret in Skyvern. Saving replaces the whole credential, so enter your master password again too. Saving Bitwarden settings with the `skyvern_bitwarden_config_set` MCP tool also replaces the whole credential and removes any saved API key.

To change or remove a vault, click **Edit** on the tile, then update the fields or click **Clear Token** / **Clear Credential** / **Clear Configuration**.

How agents pick a vault item at run time, and how to reference items in an agent's inputs, is on [Credentials and 2FA](https://skyvern.com/docs/credentials.md).

## MCP

Click **Set up →** on the **MCP** tile, or **Integrations → MCP** in the sidebar, to open **Connect Skyvern with MCP** at `/integrations/mcp`. Pick your client: **Claude Code**, **Cursor**, **Codex CLI**, **ChatGPT**, **Claude Desktop**, **Windsurf**, **Hermes** or **OpenClaw**. The page shows the recommended setup for that client, with commands you can copy. Browser sign-in (OAuth) methods need no API key. API key methods come pre-filled with your key.

![Connect Skyvern with MCP with Claude Code selected and the Browser sign-in steps](https://mintcdn.com/skyvern/amcBKP0IBwdNswdN/images/cloud/cloud-integrations-mcp.png?fit=max\&auto=format\&n=amcBKP0IBwdNswdN\&q=85\&s=0c37c3a3e2cd42e86f7df703cbcbe056)

Per-client details, tool scopes and troubleshooting are on [MCP and coding agents](https://skyvern.com/docs/developers/getting-started/mcp.md).

## Automation platforms

Build a workflow in Skyvern before adding its run action in a builder. All four connections use an organization API key from [Settings → API keys](https://skyvern.com/docs/cloud/account.md#api-keys), sent in the `x-api-key` header. Save the key in the builder's Skyvern connection, not in a workflow input. Organization keys have full access to your organization; scoped API keys are coming.

For Skyvern Cloud, the API base URL is `https://api.skyvern.com`. For a self-hosted deployment, use its API origin and make sure the builder can reach it. The n8n node exposes a **Base URL** credential field (default: `https://api.skyvern.com`); enter the origin only, without `/api/v1`, because the node adds API paths itself. The Zapier, Make and Workato listings do not show a custom base URL field; contact Skyvern Support to confirm self-hosted support before connecting.

### Zapier

[Add Skyvern from the Zapier listing](https://zapier.com/apps/skyvern/integrations), create a connection with your organization API key, then add **Run a Workflow** to your Zap. Use **Get a Workflow** with the returned workflow run ID to retrieve its result. The current Run a Workflow action's workflow and input fields may not load reliably; verify the workflow exists and the connection uses the right key, but setup alone cannot fix an app-side loading issue.

### Make

[Add a Skyvern module from the Make listing](https://www.make.com/en/integrations/skyvern-ai) to your scenario and click **Create a connection**. Enter your organization API key, then choose **Run a Workflow** or **Run a Task**. Use **Get a Workflow** or **Get a Task** with the returned run ID to retrieve the result.

### n8n

The [verified Skyvern node listing](https://n8n.io/integrations/skyvern/) requires a one-time install by an n8n instance owner or admin: open the Nodes panel (+), find Skyvern under **More from the community**, and select **Install**. Everyone on the instance can then add it to workflows. On n8n Cloud, the owner controls verified-node availability in the Cloud Admin Panel; on self-hosted n8n, the admin controls it through environment variables. Create a Skyvern API credential with your organization key and, for self-hosted Skyvern, the API **Base URL**. Choose the **Workflow** or **Task** resource and a dispatch operation, then use the matching Get operation with the returned run ID. For **Get Workflow**, also select the same workflow (or provide its ID) in **Workflow Name or ID**, and enter the returned run ID in **Workflow Run ID**. The node's workflow selector lists at most 100 workflows.

### Workato

[Add the Skyvern connector from the Workato listing](https://www.workato.com/integrations/skyvern) to a recipe and create its connection with your organization API key. Choose **Run a Workflow** or **Create and Run Task**. Workato's **Get Workflow** action looks up a workflow by workflow ID; it does not retrieve a workflow run. Pair **Create and Run Task V2** with **Get Task V2** and its returned `tsk_v2_...` ID; for v1 tasks, use **Get Task** with the task ID.

Workflow run IDs start with `wr_`; v1 task IDs start with `tsk_`, and Task V2 IDs start with `tsk_v2_`. A run may finish after the builder's action returns. Use the matching Get action when that builder provides one, or watch the run in Skyvern history. If a Run action offers a webhook callback URL, you can provide one that Skyvern can reach instead of polling.

> [!TIP]
>
> Watch progress in the Skyvern app while you test. Every run started from a platform appears in your run history like any other run. See [Runs and schedules](https://skyvern.com/docs/cloud/runs.md).

## Next

> [card] [Credentials and 2FA](https://skyvern.com/docs/credentials.md)
>
> Store logins and use vault items in agents

> [card] [Account and API keys](https://skyvern.com/docs/cloud/account.md)
>
> Find and rotate the key the platforms need

> [card] [MCP and coding agents](https://skyvern.com/docs/developers/getting-started/mcp.md)
>
> Drive Skyvern from Claude, Cursor or Codex


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.