How to connect Chaser to OpenClaw
Connect Chaser to OpenClaw with ClawLink: paste your Chaser key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine.
ChaserAPI KEYMCPChaser is an accounts receivable automation software that helps businesses automate invoice reminders and get paid faster.. Once connected, OpenClaw can read and act on Chaser from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Chaser 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 Chaser setup: install one ClawHub skill, connect Chaser in the browser, and OpenClaw can call real Chaser 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 Chaser.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Chaser
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Chaser?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Chaser in the ClawLink dashboard — paste your Chaser API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Chaser, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Chaser is connected in the dashboard, that agent calls the same 30 Chaser tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Chaser MCP for OpenClaw
Looking for a Chaser MCP server for OpenClaw? ClawLink connects Chaser to OpenClaw and exposes 30 Chaser tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Chaser integration works the same way.
What the OpenClaw Chaser integration can do
30 Chaser tools are ready for OpenClaw once the account is connected. The 29 below are the ones people reach for most; your agent can call all 30.
29 of 30 Chaser tools for OpenClaw
| Tool | What it does |
|---|---|
Get contact person chaser_get_contact_person | Get a specific contact person by ID for a customer |
Get credit note by ID chaser_get_credit_note_by_id | Retrieve detailed information for a specific credit note by its ID |
Get credit notes chaser_get_credit_notes | Retrieves a list of credit notes from Chaser |
Get current organisation chaser_get_current_organisation | Retrieve information about the current organisation associated with the API credentials |
Get customer by ID chaser_get_customer_by_id | Retrieve detailed information for a specific customer by their Chaser customer ID |
Get customers chaser_get_customers | Retrieve a list of all customers associated with the organization |
Get invoice chaser_get_invoice | Retrieve detailed information for a specific invoice by its ID |
Get organization chaser_get_organization | Retrieve information about the connected organizations |
Get overpayment chaser_get_overpayment | Retrieve detailed information for a specific overpayment by its ID |
Get status chaser_get_status | Check the status of the Chaser API |
List contact persons chaser_list_contact_persons | Retrieve contact persons for a specific customer |
List invoices chaser_list_invoices | Retrieve invoices with pagination and filtering |
List overpayments chaser_list_overpayments | Retrieve overpayments from Chaser with pagination and filtering |
Create contact person chaser_create_contact_person | Create a new contact person for a customer in Chaser |
Create invoice chaser_create_invoice | Create a new invoice record in the organization |
Create overpayment chaser_create_overpayment | Creates a new overpayment record in Chaser for tracking customer overpayments |
Post credit note chaser_post_credit_note | Creates a new credit note record in Chaser for tracking customer credits |
Post customer chaser_post_customer | Create a new customer record in Chaser |
Put credit note chaser_put_credit_note | Update an existing credit note in Chaser |
Put customer chaser_put_customer | Update an existing customer's information using their unique Chaser customer ID |
Put invoice chaser_put_invoice | Update an existing invoice in Chaser by its internal ID |
Update contact person chaser_update_contact_person | Update a contact person for a customer in Chaser |
Update overpayment chaser_update_overpayment | Update an overpayment record in Chaser |
Upload invoice PDF chaser_upload_invoice_pdf | Upload a PDF file to an existing invoice in Chaser |
Upsert bulk customers chaser_upsert_bulk_customers | Bulk upsert up to 100 customers in a single operation |
Upsert contact persons chaser_upsert_contact_persons | Bulk insert or update contact persons for a customer |
Upsert credit notes bulk chaser_upsert_credit_notes_bulk | Bulk upsert up to 100 credit notes in a single request |
Upsert invoices chaser_upsert_invoices | Bulk upsert up to 100 invoices in a single request |
Upsert overpayments bulk chaser_upsert_overpayments_bulk | Bulk upsert up to 100 overpayments in Chaser, matching by overpayment_id |
Try it: find the Chaser tool you need
Browse the 29 Chaser tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chaser, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Chaser, 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 Chaser working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Chaser API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Chaser 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 Chaser. | 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 Chaser actions to the runtime in a format your agent can reliably use. | 30 tools for Chaser are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Chaser 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 Chaser in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Chaser key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Chaser skill but can't call the tools
The ClawHub skill teaches OpenClaw about Chaser, but the calls run through the ClawLink plugin and your connected account. Make sure Chaser 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 Chaser 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 Chaser tools
Chaser 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 Chaser 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.
Chaser 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 Chaser has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Chaser integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Chaser: link your Chaser account once in the browser and OpenClaw can call the Chaser API through 30 ready-made tools — no custom code or token handling.
How do I add Chaser to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Chaser skill from ClawHub, then you click Connect in the dashboard to authorize Chaser. OpenClaw calls the tools from the next message — no config files, and the Chaser key you paste is stored server-side instead of in your environment.
How long does it take to connect Chaser to OpenClaw?
About two minutes. Sign in, click Connect next to Chaser in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Chaser 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 Chaser working from chat.
OpenClaw installed the Chaser skill but can't call the tools
The ClawHub skill teaches OpenClaw about Chaser, but the calls run through the ClawLink plugin and your connected account. Make sure Chaser 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.
