Skip to content
Back to search

connectors

Connect your agent to the apps you already use - with or without Zapier.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/zapier/connectors with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/zapier/connectors'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/zapier--connectors/badge.svg)](/listings/zapier--connectors)

HTML

<a href="/listings/zapier--connectors"><img src="/api/listings/zapier--connectors/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 83 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Zapier Connectors
  2. [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/zapier/connectors)
  3. > [!NOTE]
  4. > **Status: prototype.** First-cohort connectors are being written to validate the artifact shape against eval, installation and consumption from various agent harnesses. **Treat nothing here as a stable contract.** Pre-1.0 (`0.x`): breaking changes ship as a minor bump, features and fixes as a patch. Pin with a caret (`^0.x.y`) so you don't pick up a breaking minor automatically. Licensed under the [Elastic License 2.0](./LICENSE).
  5. A growing catalog of agent-callable tools for the 9k+ apps Zapier integrates with. Each tool is **simultaneously** an [agentskills.io](https://agentskills.io/specification)-compliant skill artifact and an [MCP `Tool`](https://modelcontextprotocol.io/specification/2025-06-18/schema#tool)-shaped TypeScript module. The combined shape is the contribution: neither standard defines it alone.
  6. The catalog is designed to run **anywhere**:
  7. - as installable agentskills.io skills in any compatible client (Cursor, Claude Code, Codex, Copilot, VS Code, Gemini CLI, Goose, OpenCode, …)
  8. - as native MCP tools registered into any MCP server's `tools/list`
  9. - inside Zapier surfaces (Sidekick, the Zapier MCP server, code-based Zaps) — Zapier is the _easy_ path, not the only path
  10. - outside Zapier with user-held credentials via each connector's declared `connectionResolvers`
  11. ## Using a connector
  12. A connector is one folder, many surfaces — there are four ways to reach for it:
  13. 1. **Install as an agentskills.io skill** in a compatible AI client — Cursor, Claude Code, Codex, Copilot, Goose, and ~40 others. The agent reads `SKILL.md` and either (a) executes the connector's scripts directly when a task calls for it, or (b) uses the scripts + `references/` as recipes when generating code.
  14. 2. **Add as a dependency** in your own TypeScript / Node code. Named imports give each script's wrapped `.run(input, opts)`; the default import adds the structured object (`scripts`, `connectionResolvers`) for direct in-process calls. Pass auth as one `[<resolver>:]<value>` string: `{ connection: "env:NOTION_TOKEN" }` (or `{ connections: { <slot>: ... } }` for multi-slot scripts).
  15. 3. **Call as a CLI** — `echo '{...}' | npx @zapier/notion-connector run <script>` parses JSON on stdin/argv and prints the upstream API response. Cron, GitHub Actions, Terraform, anything that shells out.
  16. 4. **Run as a local MCP server** via the bundled CLI — `npx @zapier/notion-connector mcp` exposes every script as a native MCP tool over stdio, and the connector's `SKILL.md` + `references/*.md` as MCP resources, no consumer code required.
  17. Each connector documents its own scripts, auth modes, and setup in its own `README.md` (e.g. [`apps/notion/README.md`](apps/notion/README.md)).
  18. ### In your own code
  19. ```ts
  20. import notion from "@zapier/notion-connector";
  21. const result = await notion.scripts.search.run(
  22. { query: "Q4 planning" },
  23. { connection: "env:NOTION_TOKEN" },
  24. );
  25. // Or import one script's run function when you already know the name:
  26. import { search } from "@zapier/notion-connector";
  27. await search({ query: "Q4 planning" }, { connection: "env:NOTION_TOKEN" });
  28. ```
  29. Auth is one `[<resolver>:]<value>` connection string per slot — `env:NOTION_TOKEN` reads the token from `process.env.NOTION_TOKEN`, `zapier:<connection-id>` routes through Zapier-managed auth, and a bare value is claimed by the first matching resolver.
  30. ### Running a tool locally
  31. This is what way 1 does under the hood, and — swapping `node <script>` for `npx @zapier/notion-connector run <script>` — also what way 3 (the CLI) does from the published package. Each script takes JSON on stdin or `argv[1]` and resolves auth from a `--connection [<resolver>:]<value>` flag against the connector's resolvers. The connection value is a _selector_ (an env-var name or a connection id), not the secret itself, so it's safe to pass on argv; the `env:` resolver still reads the actual token from the named environment variable. Auth via a Zapier connection is the recommended path; direct mode is the fallback for callers who don't want a Zapier dep:
  32. ```bash
  33. # With Zapier — Zapier connection UUID, auth handled by Zapier (recommended)
  34. # Find a connection UUID with: zapier-sdk list-connections notion
  35. echo '{"query":"foo"}' | node apps/notion/scripts/search.ts --connection zapier:<connection-id>
  36. # Direct mode — your own 3P credentials (no Zapier needed); the token stays in env
  37. echo '{"query":"foo"}' | NOTION_TOKEN=secret_xxx node apps/notion/scripts/search.ts --connection env:NOTION_TOKEN
  38. # The `<resolver>:` prefix is optional — a bare value goes to the first resolver
  39. # that claims it (a UUID → `zapier`, a set env-var name → `env`):
  40. echo '{"query":"foo"}' | node apps/notion/scripts/search.ts --connection <connection-id>
  41. # From the published package, `node <script>` becomes the bundled CLI (way 3) —
  42. # same stdin/argv + `--connection` contract, no checkout needed:
  43. echo '{"query":"foo"}' | npx @zapier/notion-connector run search --connection env:NOTION_TOKEN
  44. # Run with `--help` to see each script's input schema and available resolvers:
  45. node apps/notion/scripts/search.ts --help
  46. ```
  47. The connector's `SKILL.md` describes the trade-offs between the two modes (setup steps, where the third-party credential lives, how revocation works).
  48. Node (22.18+) runs the TypeScript directly — `npm install` the connector's deps first. Bun works too and auto-installs deps on first run.
  49. ### Cloning the source
  50. You don't need to clone the source code for a connector to use it; various options for installing and/or using a connector directly are explained above. However, if you do want the actual source instead — to read a script's code, browse `references/`, run a connector's tests, or hack on it — clone with a path filter so you only fetch the `apps/<slug>` folders you care about, not the whole catalog:
  51. ```bash
  52. git clone --filter=blob:none --sparse https://github.com/zapier/connectors.git
  53. cd connectors
  54. git sparse-checkout set apps/notion apps/trello # only the connectors you need
  55. ```
  56. Each `apps/<slug>` is standalone-installable — no root `npm install` or workspace bootstrap is required. Just `cd apps/<slug> && npm install`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.