---
title: Zapier Integration
---

# Zapier Integration

## What it is

Connects Claude sessions to 8,000+ apps via Zapier's remote MCP server. When enabled, every spawned Claude session gets Zapier tools injected automatically — agents can trigger Zaps, read data from connected apps, and manage workflows without any per-session setup.

## Where to find it

Everything is set up in **Settings > Channels > Zapier**, where a toggle enables the channel and a field takes the server URL. The URL itself comes from Zapier's own site at [mcp.zapier.app](https://mcp.zapier.app), and the individual app connections are enabled on Zapier's configuration page rather than in Omniscio.

## How it behaves

### Setup flow

1. Go to [mcp.zapier.app](https://mcp.zapier.app) and sign in (or create a free Zapier account)
2. Create a new MCP server — Zapier generates a unique URL
3. In Omniscio, go to **Settings > Channels > Zapier**
4. Enable the toggle and paste the server URL
5. On Zapier's configuration page, enable the specific app actions you want (Gmail, Slack, Sheets, Shopify, etc.)

Each app connection uses OAuth handled by Zapier's web UI — Omniscio never touches those credentials.

### What sessions can do

With Zapier enabled, Claude sessions have access to tools like:

- **discover_zapier_actions** — find available app integrations
- **enable_zapier_action** / **disable_zapier_action** — toggle specific actions
- **execute_zapier_read_action** — read data from connected apps
- **execute_zapier_write_action** — write data / trigger actions
- **list_zapier_skills** / **get_zapier_skill** — manage saved workflows

### Auth model

Zapier MCP uses URL-embedded authentication — the server URL itself is the credential. No separate API key or OAuth flow at the MCP protocol level. Individual app connections (Gmail, Slack, etc.) use OAuth managed entirely by Zapier's web UI.

### Rate limits

Zapier task usage counts toward the user's Zapier plan quota (free: 100 tasks/month, paid plans increase). No separate MCP-specific rate limit.

## For agents

### How it works

Omniscio injects the user's Zapier MCP server URL into each session's `.mcp.json` at spawn time, alongside any other MCP servers (MemPalace, KMS). The Zapier server is **remote** (URL-based SSE transport), unlike the local subprocess servers — no bundled binary, no DB path, just a URL.

### Architecture

| Component     | File                                                               | Purpose                                                |
| ------------- | ------------------------------------------------------------------ | ------------------------------------------------------ |
| Entry builder | `src/main/services/zapier/mcp-config-entry.ts`                     | Builds `McpRemoteServerEntry` with the user's URL      |
| Orchestrator  | `src/main/services/mcp/mcp-config-orchestrator.ts`                     | Composes Zapier alongside mempalace/kms in `.mcp.json` |
| Settings      | `src/renderer/src/features/settings/sections/channels/ZapierSettings.tsx`            | Toggle + URL input UI                                  |
| Definitions   | `src/renderer/src/features/settings/sections/channels/ZapierSettings-definitions.ts` | Setting definitions for search index                   |
| Registry      | `src/shared/integration-registry.ts`                               | `zapier` channel-adapter entry                         |

### Feature flag

- **Setting**: `zapierEnabled` (default `false`)
- **URL setting**: `zapierMcpServerUrl` (default `''`)
- Both must be truthy for the MCP entry to be injected
- Force-disabled for search and Ask-Omniscio sessions (same as MemPalace/KMS)

## Related

What an MCP server is and how the other ones are wired into a session is on [MCP servers](mcp-servers.md). The pre-built app connections that do not need Zapier at all are on [Composio](composio.md), and the automation marketplace where ready-made integrations are installed is on [Automation marketplace](automation-marketplace.md).