# How to connect Proabono to OpenClaw (paste one key, 64 tools) > Connect Proabono to OpenClaw with ClawLink: paste your Proabono key once and 64 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/proabono The usual route to Proabono 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 Proabono setup: install one ClawHub skill, connect Proabono in the browser, and OpenClaw can call real Proabono 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 Proabono. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Proabono** — 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 proabono # connect Proabono (browser OAuth) npx -y @useclawlink/cli actions proabono # list available actions npx -y @useclawlink/cli run proabono --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 Proabono in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your Proabono account details once. Verify the connection by asking OpenClaw: > Pull the relevant data from Proabono, 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 Proabono is connected in the dashboard, that agent calls the same 64 Proabono 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). ## Proabono MCP for OpenClaw Looking for a Proabono MCP server for OpenClaw? ClawLink connects Proabono to OpenClaw and exposes 64 Proabono 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 Proabono integration](https://claw-link.dev/hermes/proabono) works the same way. ## What the OpenClaw Proabono integration can do 64 Proabono 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 64. ### 30 of 64 Proabono tools for OpenClaw | Tool | What it does | |---|---| | **Get customer** `proabono_get_customer` | Retrieve a single customer by ID from ProAbono Backoffice API | | **Get customer billing** `proabono_get_customer_billing` | Retrieve a customer's billing address via the Backoffice API | | **Get customer billing address** `proabono_get_customer_billing_address` | Retrieve the billing address for a customer by reference from ProAbono API | | **Get customer by reference** `proabono_get_customer_by_reference` | Retrieve a customer by their reference identifier from ProAbono API | | **Get customer payment settings** `proabono_get_customer_payment_settings` | Retrieve customer payment settings via the Backoffice API | | **Get discount** `proabono_get_discount` | Retrieve a discount by ID via the Backoffice API | | **Get feature** `proabono_get_feature` | Retrieve a feature by ID from ProAbono Backoffice API | | **Get invoice** `proabono_get_invoice` | Retrieve a specific invoice or credit note by ID from ProAbono | | **Get offer** `proabono_get_offer` | Retrieve a single offer by its ID from ProAbono Backoffice API | | **Get subscription by customer** `proabono_get_subscription_by_customer` | Retrieve a subscription by customer reference from ProAbono | | **Get subscription creation quote** `proabono_get_subscription_creation_quote` | Get a pricing quote for creating a new subscription without actually creating it | | **Get usage** `proabono_get_usage` | Retrieve a single usage record for a specific feature and customer combination from ProAbono | | **Get usages for customer** `proabono_get_usages_for_customer` | Retrieve usage data for customers from ProAbono | | **List balance lines** `proabono_list_balance_lines` | List all balance lines from ProAbono | | **List business localization** `proabono_list_business_localization` | List localization entries by business from ProAbono via the HostedPages API | | **List businesses** `proabono_list_businesses` | List all businesses from ProAbono via the Backoffice API | | **List customer moves** `proabono_list_customer_moves` | List all customer balance moves via the ProAbono Backoffice API | | **List customers** `proabono_list_customers` | List all customers from ProAbono via the Backoffice API | | **List customers by feature** `proabono_list_customers_by_feature` | List customers that have access to a specific feature via the ProAbono API | | **List discounts** `proabono_list_discounts` | List all discounts from ProAbono's Backoffice API | | **List features** `proabono_list_features` | List all features via the ProAbono Backoffice API | | **List gateway accounts** `proabono_list_gateway_accounts` | List payment gateway accounts from ProAbono Backoffice API | | **List gateway permissions** `proabono_list_gateway_permissions` | List gateway permissions from ProAbono API | | **List gateway requests** `proabono_list_gateway_requests` | List gateway requests from ProAbono | | **List gateway transactions** `proabono_list_gateway_transactions` | List gateway transactions from ProAbono | | **List invoice lines** `proabono_list_invoice_lines` | List all invoice lines from ProAbono via the Backoffice API | | **List invoices** `proabono_list_invoices` | List all invoices and credit notes from ProAbono Backoffice API | | **List invoices by customer** `proabono_list_invoices_by_customer` | List invoices for a specific customer by their reference identifier from ProAbono API | | **List offers** `proabono_list_offers` | List all subscription offers (plans) from ProAbono Backoffice API | | **List payments** `proabono_list_payments` | List all payments from ProAbono Backoffice API | ## Example prompts **Get Customer** > Pull the relevant data from Proabono, summarize it in plain English, and point out anything that needs attention. **Get Customer Billing** > Pull the relevant data from Proabono, summarize it in plain English, and point out anything that needs attention. **Get Customer Billing Address** > Pull the relevant data from Proabono, summarize it in plain English, and point out anything that needs attention. **Get Customer By Reference** > Pull the relevant data from Proabono, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential 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 Proabono working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right Proabono credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link Proabono without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Proabono. | 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 Proabono actions to the runtime in a format your agent can reliably use. | 64 tools for Proabono are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Proabono 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 Proabono in the browser, and the 64 tools above work from chat. There is no SDK and no config file, and the Proabono 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 Proabono skill but can't call the tools The ClawHub skill teaches OpenClaw about Proabono, but the calls run through the ClawLink plugin and your connected account. Make sure Proabono 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 Proabono 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 Proabono tools Proabono 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 Proabono 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. ### Proabono 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. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for Proabono. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw Proabono integration? Yes. ClawLink is the fastest way to connect OpenClaw to Proabono: link your Proabono account once in the browser and OpenClaw can call the Proabono API through 64 ready-made tools — no custom code or token handling. ### How do I add Proabono to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Proabono skill from ClawHub, then you click Connect in the dashboard to authorize Proabono. OpenClaw calls the tools from the next message — no config files, and the Proabono key you paste is stored server-side instead of in your environment. ### How long does it take to connect Proabono to OpenClaw? About two minutes. Sign in, click Connect next to Proabono in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Proabono up myself? The alternative to ClawLink is usually manual credential 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 Proabono working from chat. ### OpenClaw installed the Proabono skill but can't call the tools The ClawHub skill teaches OpenClaw about Proabono, but the calls run through the ClawLink plugin and your connected account. Make sure Proabono 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 - [OpenClaw Cloudcart integration](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently. - [Connect Wix](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings - [OpenClaw Baselinker integration](https://claw-link.dev/openclaw/baselinker) — BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.