# How to connect Bannerbear to OpenClaw (paste one key, 33 tools) > Connect Bannerbear to OpenClaw with ClawLink: paste your Bannerbear key once and 33 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/bannerbear The usual route to Bannerbear 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 Bannerbear setup: install one ClawHub skill, connect Bannerbear in the browser, and OpenClaw can call real Bannerbear 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 Bannerbear. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Bannerbear** — 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 bannerbear # connect Bannerbear (browser OAuth) npx -y @useclawlink/cli actions bannerbear # list available actions npx -y @useclawlink/cli run bannerbear --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 Bannerbear in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bannerbear API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Bannerbear, summarize it in plain English, and point out anything that needs attention. ### 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 Bannerbear is connected in the dashboard, that agent calls the same 33 Bannerbear 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). ## Bannerbear MCP for OpenClaw Looking for a Bannerbear MCP server for OpenClaw? ClawLink connects Bannerbear to OpenClaw and exposes 33 Bannerbear 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 Bannerbear integration](https://claw-link.dev/hermes/bannerbear) works the same way. ## What the OpenClaw Bannerbear integration can do 33 Bannerbear tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 33. ### 30 of 33 Bannerbear tools for OpenClaw | Tool | What it does | |---|---| | **Get account info** `bannerbear_get_account_info` | Retrieves Bannerbear account information including subscription plan, API usage, and quota | | **Get animated gif** `bannerbear_get_animated_gif` | Retrieve a single Animated Gif object by its unique identifier (UID) | | **Get auth** `bannerbear_get_auth` | Verify API authentication and check which project the API key is scoped to | | **Get fonts** `bannerbear_get_fonts` | Retrieves a list of all available fonts in Bannerbear | | **Get image** `bannerbear_get_image` | Retrieves a single Image object by its unique identifier (UID) | | **Get project** `bannerbear_get_project` | Retrieves detailed information about a specific Bannerbear project by its unique identifier | | **Get screenshot** `bannerbear_get_screenshot` | Retrieve a single Screenshot object referenced by its unique ID | | **Get signed bases** `bannerbear_get_signed_bases` | Retrieves a list of signed bases for a specific template | | **Get template** `bannerbear_get_template` | Retrieve a single template by its unique ID with layer defaults | | **Get template set** `bannerbear_get_template_set` | Retrieves detailed information about a specific template set using its unique identifier (UID) | | **Get webhook** `bannerbear_get_webhook` | Retrieves a single Webhook object by its unique ID | | **List animated gifs** `bannerbear_list_animated_gifs` | Lists all animated GIFs in a Bannerbear project | | **List collections** `bannerbear_list_collections` | Lists all collections in a Bannerbear project | | **List effects** `bannerbear_list_effects` | List all available image effects in Bannerbear | | **List images** `bannerbear_list_images` | Lists all images in a Bannerbear project | | **List projects** `bannerbear_list_projects` | Lists all projects in a Bannerbear account | | **List screenshots** `bannerbear_list_screenshots` | Lists all screenshots in a Bannerbear project | | **List template sets** `bannerbear_list_template_sets` | List all template sets inside a project with pagination support | | **List templates** `bannerbear_list_templates` | Retrieves a list of all templates available in your Bannerbear project | | **List video templates** `bannerbear_list_video_templates` | Retrieves a list of all video templates available in your Bannerbear project | | **List videos** `bannerbear_list_videos` | Retrieves a list of all videos created in your Bannerbear account | | **Create project** `bannerbear_create_project` | Creates a new Bannerbear project with the specified name and optional settings | | **Create signed base** `bannerbear_create_signed_base` | Create a signed URL base for a template | | **Create template** `bannerbear_create_template` | Create a new blank template in a Bannerbear project | | **Create template set** `bannerbear_create_template_set` | Create a new template set by grouping multiple templates together | | **Create video template** `bannerbear_create_video_template` | Create a new video template for video generation in Bannerbear | | **Create webhook** `bannerbear_create_webhook` | Create a project-level webhook that fires for all events of a specific type | | **Hydrate project** `bannerbear_hydrate_project` | Hydrate a project by copying templates from another project | | **Import template** `bannerbear_import_template` | Import templates from the Bannerbear template library or from other projects | | **Join pdfs** `bannerbear_join_pdfs` | Merges multiple PDF files into a single combined PDF document | ## Example prompts **Get Account Info** > Pull the relevant data from Bannerbear, summarize it in plain English, and point out anything that needs attention. **Get Animated Gif** > Pull the relevant data from Bannerbear, summarize it in plain English, and point out anything that needs attention. **Get Auth** > Pull the relevant data from Bannerbear, summarize it in plain English, and point out anything that needs attention. **Get Fonts** > Pull the relevant data from Bannerbear, 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 Bannerbear working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Bannerbear API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bannerbear 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 Bannerbear. | 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 Bannerbear actions to the runtime in a format your agent can reliably use. | 33 tools for Bannerbear are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Bannerbear 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 Bannerbear in the browser, and the 33 tools above work from chat. There is no SDK and no config file, and the Bannerbear 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 Bannerbear skill but can't call the tools The ClawHub skill teaches OpenClaw about Bannerbear, but the calls run through the ClawLink plugin and your connected account. Make sure Bannerbear 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 Bannerbear 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 Bannerbear tools Bannerbear 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 Bannerbear 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. ### Bannerbear 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 Bannerbear has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Bannerbear integration? Yes. ClawLink is the fastest way to connect OpenClaw to Bannerbear: link your Bannerbear account once in the browser and OpenClaw can call the Bannerbear API through 33 ready-made tools — no custom code or token handling. ### How do I add Bannerbear to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bannerbear skill from ClawHub, then you click Connect in the dashboard to authorize Bannerbear. OpenClaw calls the tools from the next message — no config files, and the Bannerbear key you paste is stored server-side instead of in your environment. ### How long does it take to connect Bannerbear to OpenClaw? About two minutes. Sign in, click Connect next to Bannerbear in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Bannerbear 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 Bannerbear working from chat. ### OpenClaw installed the Bannerbear skill but can't call the tools The ClawHub skill teaches OpenClaw about Bannerbear, but the calls run through the ClawLink plugin and your connected account. Make sure Bannerbear 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 tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](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