# How to connect Passcreator to OpenClaw (paste one key, 11 tools) > Connect Passcreator to OpenClaw with ClawLink: paste your Passcreator key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/passcreator The usual route to Passcreator access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Passcreator setup: install one ClawHub skill, connect Passcreator in the browser, and OpenClaw can call real Passcreator actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Passcreator. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Passcreator** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect passcreator # connect Passcreator (browser OAuth) npx -y @useclawlink/cli actions passcreator # list available actions npx -y @useclawlink/cli run passcreator --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Passcreator in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Passcreator API key once. Verify the connection by asking OpenClaw: > Use Passcreator to check pass existence and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Passcreator is connected in the dashboard, that agent calls the same 11 Passcreator tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Passcreator MCP for OpenClaw Looking for a Passcreator MCP server for OpenClaw? ClawLink connects Passcreator to OpenClaw and exposes 11 Passcreator tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Passcreator integration](https://claw-link.dev/hermes/passcreator) works the same way. ## What the OpenClaw Passcreator integration can do 11 Passcreator tools are ready for OpenClaw once the account is connected. ### All 11 Passcreator tools for OpenClaw | Tool | What it does | |---|---| | **Check pass existence** `passcreator_check_pass_existence` | Check if a pass exists for a given ID | | **Get app configuration** `passcreator_get_app_configuration` | Retrieves detailed information about an App Configuration by its identifier | | **Get process status** `passcreator_get_process_status` | Get the current status and progress of a bulk operation including any errors | | **Get signing public key** `passcreator_get_signing_public_key` | Obtain the public key needed to verify signatures from the placeholder sign() function | | **List app configurations** `passcreator_list_app_configurations` | Retrieves all App Configurations for your Passcreator account | | **List app scans** `passcreator_list_app_scans` | Retrieves a paginated list of scans for a given app configuration | | **List pass templates** `passcreator_list_pass_templates` | Retrieves all pass templates for your Passcreator account | | **List passes** `passcreator_list_passes` | List and search wallet passes from Passcreator using the v3 API | | **Create app scan** `passcreator_create_app_scan` | Create a new App Scan in PassCreator | | **Send bulk push notifications** `passcreator_send_bulk_push_notifications` | Send push notifications to multiple wallet passes simultaneously (up to 500 passes) | | **Update passes bulk** `passcreator_update_passes_bulk` | Bulk update multiple wallet passes using filter criteria | ## Example prompts **Check Pass Existence** > Use Passcreator to check pass existence and walk me through the result in plain English. **Get App Configuration** > Pull the relevant data from Passcreator, summarize it in plain English, and point out anything that needs attention. **Get Process Status** > Pull the relevant data from Passcreator, summarize it in plain English, and point out anything that needs attention. **Get Signing Public Key** > Pull the relevant data from Passcreator, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Passcreator working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Passcreator API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Passcreator account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Passcreator. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Passcreator actions to the runtime in a format your agent can reliably use. | 11 tools for Passcreator are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Passcreator to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Passcreator in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Passcreator key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Passcreator skill but can't call the tools The ClawHub skill teaches OpenClaw about Passcreator, but the calls run through the ClawLink plugin and your connected account. Make sure Passcreator is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Passcreator from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Passcreator tools Passcreator tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Passcreator call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Passcreator returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Passcreator has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Passcreator integration? Yes. ClawLink is the fastest way to connect OpenClaw to Passcreator: link your Passcreator account once in the browser and OpenClaw can call the Passcreator API through 11 ready-made tools — no custom code or token handling. ### How do I add Passcreator to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Passcreator skill from ClawHub, then you click Connect in the dashboard to authorize Passcreator. OpenClaw calls the tools from the next message — no config files, and the Passcreator key you paste is stored server-side instead of in your environment. ### How long does it take to connect Passcreator to OpenClaw? About two minutes. Sign in, click Connect next to Passcreator in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Passcreator up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Passcreator working from chat. ### OpenClaw installed the Passcreator skill but can't call the tools The ClawHub skill teaches OpenClaw about Passcreator, but the calls run through the ClawLink plugin and your connected account. Make sure Passcreator is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Connect Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences