How to connect Ascora to OpenClaw
Connect Ascora to OpenClaw with ClawLink: paste your Ascora key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine.
AscoraAPI KEYMCPAscora is a cloud-based field service management software designed to streamline operations for service-based businesses, offering features such as job scheduling, invoicing, customer management, and mobile access.. Once connected, OpenClaw can read and act on Ascora from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Ascora 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 Ascora setup: install one ClawHub skill, connect Ascora in the browser, and OpenClaw can call real Ascora 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 Ascora.
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 Ascora
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Ascora?"
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 Ascora in the ClawLink dashboard — paste your Ascora API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Ascora, 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 Ascora is connected in the dashboard, that agent calls the same 23 Ascora tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Ascora MCP for OpenClaw
Looking for a Ascora MCP server for OpenClaw? ClawLink connects Ascora to OpenClaw and exposes 23 Ascora tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Ascora integration works the same way.
What the OpenClaw Ascora integration can do
23 Ascora tools are ready for OpenClaw once the account is connected. The 22 below are the ones people reach for most; your agent can call all 23.
22 of 23 Ascora tools for OpenClaw
| Tool | What it does |
|---|---|
Get contact ascora_get_contact | Retrieve details of a specific contact by their unique identifier |
Get customer ascora_get_customer | Retrieve details of a specific customer by their unique identifier |
Get customers ascora_get_customers | Retrieves all customers from the Ascora system |
Get inventory categories ascora_get_inventory_categories | Retrieves all inventory categories used to organize supplies and kits in Ascora |
Get inventory kits ascora_get_inventory_kits | Retrieves all inventory kits from Ascora |
Get inventory supplies ascora_get_inventory_supplies | Retrieves all inventory supplies with pricing and stock information from Ascora |
Get job ascora_get_job | Retrieves details of a specific job by its unique identifier |
Get jobs ascora_get_jobs | Retrieves a paginated list of jobs from Ascora with optional filtering by job type, status |
Get quote labour roles ascora_get_quote_labour_roles | Retrieves labour roles available for use in quotes from Ascora |
Get quote standard sections ascora_get_quote_standard_sections | Retrieves standard sections that can be used in quotes |
Get quote standard stages ascora_get_quote_standard_stages | Retrieves standard stages that can be used in quotes for progress tracking |
Get quotes ascora_get_quotes | Retrieves a paginated list of quotes from Ascora with optional filtering by status, date range |
Get supplier ascora_get_supplier | Retrieve details of a specific supplier by ID |
Get supplier invoices ascora_get_supplier_invoices | Retrieves supplier invoices from Ascora with optional pagination |
Get suppliers ascora_get_suppliers | Retrieves a list of suppliers from the Ascora system |
Search jobs ascora_search_jobs | Search for jobs by various criteria including job number, customer, or address |
Create note ascora_create_note | Creates a note on an entity (customer, job, quote, etc.) in Ascora |
Create or update contact ascora_create_or_update_contact | Create a new contact or update an existing contact for a customer |
Create or update customer ascora_create_or_update_customer | Create a new customer or update an existing customer in Ascora |
Create or update supplier ascora_create_or_update_supplier | Create a new supplier or update an existing supplier in Ascora |
Create quotation ascora_create_quotation | Creates a new quotation/enquiry in Ascora for a customer |
Upload attachment ascora_upload_attachment | Upload an attachment to an entity (quote, job, customer, etc.) in Ascora |
Try it: find the Ascora tool you need
Browse the 22 Ascora 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 Ascora, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ascora, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ascora, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ascora, 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 Ascora working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Ascora API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ascora 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 Ascora. | 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 Ascora actions to the runtime in a format your agent can reliably use. | 23 tools for Ascora are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Ascora 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 Ascora in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Ascora 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 Ascora skill but can't call the tools
The ClawHub skill teaches OpenClaw about Ascora, but the calls run through the ClawLink plugin and your connected account. Make sure Ascora 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 Ascora 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 Ascora tools
Ascora 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 Ascora 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.
Ascora 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 Ascora 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 Ascora integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Ascora: link your Ascora account once in the browser and OpenClaw can call the Ascora API through 23 ready-made tools — no custom code or token handling.
How do I add Ascora to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ascora skill from ClawHub, then you click Connect in the dashboard to authorize Ascora. OpenClaw calls the tools from the next message — no config files, and the Ascora key you paste is stored server-side instead of in your environment.
How long does it take to connect Ascora to OpenClaw?
About two minutes. Sign in, click Connect next to Ascora in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Ascora 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 Ascora working from chat.
OpenClaw installed the Ascora skill but can't call the tools
The ClawHub skill teaches OpenClaw about Ascora, but the calls run through the ClawLink plugin and your connected account. Make sure Ascora 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.
