# How to connect Fireberry to OpenClaw (paste one key, 123 tools) > Connect Fireberry to OpenClaw with ClawLink: paste your Fireberry key once and 123 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/fireberry The usual route to Fireberry 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 Fireberry setup: install one ClawHub skill, connect Fireberry in the browser, and OpenClaw can call real Fireberry actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/fireberry ## Setup It takes three steps to connect OpenClaw to Fireberry. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Fireberry** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 fireberry # connect Fireberry (browser OAuth) npx -y @useclawlink/cli actions fireberry # list available actions npx -y @useclawlink/cli run fireberry --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 Fireberry in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fireberry API key once. Verify the connection by asking OpenClaw: > Create it in Fireberry for me, then confirm the important fields before you finish. ### 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 Fireberry is connected in the dashboard, that agent calls the same 123 Fireberry 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). ## Fireberry MCP for OpenClaw Looking for a Fireberry MCP server for OpenClaw? ClawLink connects Fireberry to OpenClaw and exposes 123 Fireberry 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 Fireberry integration](https://claw-link.dev/hermes/fireberry) works the same way. ## What the OpenClaw Fireberry integration can do 123 Fireberry 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 123. ### 30 of 123 Fireberry tools for OpenClaw | Tool | What it does | |---|---| | **Create a competitor** `fireberry_create_a_competitor` | Create a new competitor in Fireberry | | **Create a contact** `fireberry_create_a_contact` | Create a new contact in Fireberry CRM | | **Create a date field** `fireberry_create_a_date_field` | Create a new date field in a Fireberry object/table | | **Create a lookup field** `fireberry_create_a_lookup_field` | Create a lookup field in Fireberry CRM | | **Get a crmorder** `fireberry_get_a_crmorder` | Retrieve a specific CRM Order from Fireberry by its GUID | | **Get a meeting** `fireberry_get_a_meeting` | Retrieve a specific meeting/activity record by its unique identifier (GUID) | | **Get a note** `fireberry_get_a_note` | Retrieve a specific note record by its GUID | | **Get a phone call** `fireberry_get_a_phone_call` | Retrieve a specific phone call record from Fireberry by its GUID | | **Get a product** `fireberry_get_a_product` | Retrieve a specific product record by its GUID | | **Get a project** `fireberry_get_a_project` | Retrieve a specific project from Fireberry by its GUID | | **Get a task** `fireberry_get_a_task` | Retrieve a specific task record by its GUID | | **Get a ticket** `fireberry_get_a_ticket` | Retrieve a specific ticket (case) record by its GUID | | **Get account** `fireberry_get_account` | Retrieve a specific account record by its GUID | | **Get all accounts3** `fireberry_get_all_accounts3` | Retrieve all accounts from Fireberry CRM with pagination support | | **Get all activity logs2** `fireberry_get_all_activity_logs2` | Retrieve all activity logs from Fireberry using v2 API endpoint with pagination support | | **Get all articles** `fireberry_get_all_articles` | Retrieve all articles from Fireberry with pagination support | | **Get all assets2** `fireberry_get_all_assets2` | Retrieve all assets (account products) from Fireberry with pagination support | | **Get all business units2** `fireberry_get_all_business_units2` | Retrieve all business units from Fireberry using v2 API endpoint with pagination support | | **Get all campaigns** `fireberry_get_all_campaigns` | Retrieve all campaigns from Fireberry with pagination support | | **Get all competitors2** `fireberry_get_all_competitors2` | Retrieve all competitors from Fireberry with pagination support | | **Get all contacts** `fireberry_get_all_contacts` | Retrieve all contacts from Fireberry with pagination support | | **Get all contracts2** `fireberry_get_all_contracts2` | Retrieve all contracts from Fireberry with pagination support | | **Get all custom object records** `fireberry_get_all_custom_object_records` | Retrieve all records from a specified custom object in Fireberry with pagination support | | **Get all meetings3** `fireberry_get_all_meetings3` | Retrieve all meetings (activities) from Fireberry CRM with pagination support | | **Get all notes2** `fireberry_get_all_notes2` | Retrieve all notes from Fireberry with detailed field schema and pagination support | | **Get all objects** `fireberry_get_all_objects` | Retrieve all object type metadata from Fireberry | | **Get all order items** `fireberry_get_all_order_items` | Retrieve all order items from Fireberry with pagination support | | **Get all orders** `fireberry_get_all_orders` | Retrieve all orders from Fireberry with pagination support | | **Get all phone calls** `fireberry_get_all_phone_calls` | Retrieve all phone call records from Fireberry with pagination support | | **Get all projects2** `fireberry_get_all_projects2` | Retrieve all projects from Fireberry with pagination support | ## Example prompts **Create A Competitor** > Create it in Fireberry for me, then confirm the important fields before you finish. **Create A Contact** > Create it in Fireberry for me, then confirm the important fields before you finish. **Create A Date Field** > Create it in Fireberry for me, then confirm the important fields before you finish. **Create A Lookup Field** > Create it in Fireberry for me, then confirm the important fields before you finish. ## 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 Fireberry working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fireberry API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fireberry 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 Fireberry. | 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 Fireberry actions to the runtime in a format your agent can reliably use. | 123 tools for Fireberry are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fireberry 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 Fireberry in the browser, and the 123 tools above work from chat. There is no SDK and no config file, and the Fireberry 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 Fireberry skill but can't call the tools The ClawHub skill teaches OpenClaw about Fireberry, but the calls run through the ClawLink plugin and your connected account. Make sure Fireberry 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 Fireberry 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 Fireberry tools Fireberry 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 Fireberry 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. ### Fireberry 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 Fireberry has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Fireberry integration? Yes. ClawLink is the fastest way to connect OpenClaw to Fireberry: link your Fireberry account once in the browser and OpenClaw can call the Fireberry API through 123 ready-made tools — no custom code or token handling. ### How do I add Fireberry to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Fireberry skill from ClawHub, then you click Connect in the dashboard to authorize Fireberry. OpenClaw calls the tools from the next message — no config files, and the Fireberry key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fireberry to OpenClaw? About two minutes. Sign in, click Connect next to Fireberry in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Fireberry 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 Fireberry working from chat. ### OpenClaw installed the Fireberry skill but can't call the tools The ClawHub skill teaches OpenClaw about Fireberry, but the calls run through the ClawLink plugin and your connected account. Make sure Fireberry 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 - [HubSpot tools](https://claw-link.dev/openclaw/hubspot) — Manage contacts, deals, and pipelines - [CentralStationCRM](https://claw-link.dev/openclaw/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships. - [OpenClaw Salesforce integration](https://claw-link.dev/openclaw/salesforce) — Manage CRM data and workflows