# How to connect Acculynx to OpenClaw (paste one key, 8 tools)

> Connect Acculynx to OpenClaw with ClawLink: paste your Acculynx key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/acculynx

The usual route to Acculynx 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 Acculynx setup: install one ClawHub skill, connect Acculynx in the browser, and OpenClaw can call real Acculynx 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 Acculynx.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Acculynx** — 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 acculynx  # connect Acculynx (browser OAuth)
npx -y @useclawlink/cli actions acculynx  # list available actions
npx -y @useclawlink/cli run acculynx <action> --input '<json>'  # 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 Acculynx in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Acculynx API key once.

Verify the connection by asking OpenClaw:

> Use Acculynx to job appointment summary and walk me through the result in plain English.

### 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 Acculynx is connected in the dashboard, that agent calls the same 8 Acculynx 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).

## Acculynx MCP for OpenClaw

Looking for a Acculynx MCP server for OpenClaw? ClawLink connects Acculynx to OpenClaw and exposes 8 Acculynx 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 Acculynx integration](https://claw-link.dev/hermes/acculynx) works the same way.

## What the OpenClaw Acculynx integration can do

8 Acculynx tools are ready for OpenClaw once the account is connected.

### All 8 Acculynx tools for OpenClaw

| Tool | What it does |
|---|---|
| **Job appointment summary** `acculynx_job_appointment_summary` | Retrieves a list of appointments from the calendar associated with a specific job in AccuLynx |
| **List of calendars for the location** `acculynx_list_of_calendars_for_the_location` | Retrieves a list of calendars associated with the authenticated user or organization in AccuLynx |
| **List of contact types related to the company** `acculynx_list_of_contact_types_related_to_the_company` | Retrieves a list of all available contact types in the AccuLynx system |
| **Add job appointment** `acculynx_add_job_appointment` | This endpoint allows users to schedule the initial appointment for a specific job in the |
| **Create a contact** `acculynx_create_a_contact` | Creates a new contact in the AccuLynx system with detailed information for use in roofing and |
| **Create a job** `acculynx_create_a_job` | Creates a new job in the AccuLynx system with the provided details |
| **Create a lead** `acculynx_create_a_lead` | This endpoint creates a new lead in the AccuLynx system, specifically for residential roofing |
| **Update company representative** `acculynx_update_company_representative` | This endpoint allows you to add a company representative to a specific job within the AccuLynx |

## Example prompts

**Job Appointment Summary**

> Use Acculynx to job appointment summary and walk me through the result in plain English.

**List Of Calendars For The Location**

> List the relevant items in Acculynx, group them by priority, and recommend what OpenClaw should do next.

**List Of Contact Types Related To The Company**

> List the relevant items in Acculynx, group them by priority, and recommend what OpenClaw should do next.

**Add Job Appointment**

> Use Acculynx to add job appointment and walk me through the result in plain English.

## 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 Acculynx working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Acculynx API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Acculynx 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 Acculynx. | 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 Acculynx actions to the runtime in a format your agent can reliably use. | 8 tools for Acculynx are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Acculynx 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 Acculynx in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Acculynx 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 Acculynx skill but can't call the tools
The ClawHub skill teaches OpenClaw about Acculynx, but the calls run through the ClawLink plugin and your connected account. Make sure Acculynx 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 Acculynx 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 Acculynx tools
Acculynx 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 Acculynx 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.

### Acculynx 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 Acculynx has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Acculynx integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Acculynx: link your Acculynx account once in the browser and OpenClaw can call the Acculynx API through 8 ready-made tools — no custom code or token handling.

### How do I add Acculynx to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Acculynx skill from ClawHub, then you click Connect in the dashboard to authorize Acculynx. OpenClaw calls the tools from the next message — no config files, and the Acculynx key you paste is stored server-side instead of in your environment.

### How long does it take to connect Acculynx to OpenClaw?
About two minutes. Sign in, click Connect next to Acculynx in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Acculynx 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 Acculynx working from chat.

### OpenClaw installed the Acculynx skill but can't call the tools
The ClawHub skill teaches OpenClaw about Acculynx, but the calls run through the ClawLink plugin and your connected account. Make sure Acculynx 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](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
