# How to connect Zendesk to OpenClaw (no API keys)

> Connect Zendesk to OpenClaw with ClawLink in one click — 452 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

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

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

## Setup

It takes three steps to connect OpenClaw to Zendesk.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Zendesk** — 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 zendesk  # connect Zendesk (browser OAuth)
npx -y @useclawlink/cli actions zendesk  # list available actions
npx -y @useclawlink/cli run zendesk <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 Zendesk in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys.

Verify the connection by asking OpenClaw:

> Use Zendesk to apply zendesk macro 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 Zendesk is connected in the dashboard, that agent calls the same 452 Zendesk 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).

## Zendesk MCP for OpenClaw

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

## What the OpenClaw Zendesk integration can do

452 Zendesk 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 452.

### 30 of 452 Zendesk tools for OpenClaw

| Tool | What it does |
|---|---|
| **Apply zendesk macro** `zendesk_apply_zendesk_macro` | Preview how a Zendesk macro would affect a ticket |
| **Autocomplete users** `zendesk_autocomplete_users` | Search for Zendesk users by name prefix |
| **Count zendesk organizations** `zendesk_count_zendesk_organizations` | Count the number of organizations in Zendesk |
| **Create automation** `zendesk_create_automation` | Create a new automation in Zendesk |
| **Create custom object record** `zendesk_create_custom_object_record` | Create a new custom object record |
| **Create many tickets** `zendesk_create_many_tickets` | Create multiple Zendesk tickets in bulk |
| **Create zendesk ticket** `zendesk_create_zendesk_ticket` | Create a new Zendesk ticket |
| **Autocomplete problems** `zendesk_autocomplete_problems` | Autocomplete problems in Zendesk |
| **Check host mapping validity for existing brand** `zendesk_check_host_mapping_validity_for_existing_brand` | Check the host mapping validity for an existing brand in Zendesk |
| **Count deleted users** `zendesk_count_deleted_users` | Count deleted users in Zendesk |
| **Count user ccd tickets** `zendesk_count_user_ccd_tickets` | Count tickets where the specified user is CCD (carbon copy distribution) |
| **Count zendesk custom object records** `zendesk_count_zendesk_custom_object_records` | Count the number of records in a specific Zendesk custom object |
| **Create autocomplete tags** `zendesk_create_autocomplete_tags` | Search for Zendesk tags using autocomplete via POST request body |
| **Create suspended tickets export** `zendesk_create_suspended_tickets_export` | Export Suspended Tickets from Zendesk Support |
| **Create views preview** `zendesk_create_views_preview` | Preview a Zendesk view by constructing conditions and execution settings to see which tickets |
| **Create views preview count** `zendesk_create_views_preview_count` | Preview ticket count for a view in Zendesk |
| **Detect best locale** `zendesk_detect_best_locale` | Detect the best language/locale for the current user based on their browser settings and |
| **Download custom object record attachment** `zendesk_download_custom_object_record_attachment` | Download attachment file from a Zendesk custom object record |
| **Get about me** `zendesk_get_about_me` | Get information about the currently authenticated user in Zendesk |
| **Get account settings** `zendesk_get_account_settings` | Retrieve Zendesk account settings |
| **Get active triggers** `zendesk_get_active_triggers` | List all active ticket triggers in Zendesk |
| **Get activities count** `zendesk_get_activities_count` | Count ticket activities in Zendesk |
| **Get all zendesk organizations** `zendesk_get_all_zendesk_organizations` | Get all organizations in Zendesk |
| **Get app** `zendesk_get_app` | Get a single Zendesk app by its numeric ID |
| **Get apps installations requirements** `zendesk_get_apps_installations_requirements` | List all requirements for a Zendesk app installation |
| **Get apps location** `zendesk_get_apps_location` | Get details for a specific Zendesk app location by its numeric ID |
| **Get apps location installations** `zendesk_get_apps_location_installations` | List all apps location installations from Zendesk |
| **Get apps public key** `zendesk_get_apps_public_key` | Retrieves the public key for a specific Zendesk app |
| **Get apps public key pem** `zendesk_get_apps_public_key_pem` | Retrieves the public key for a specific Zendesk app in PEM format |
| **Get attachment** `zendesk_get_attachment` | Retrieve details of a single Zendesk attachment by its ID |

## Example prompts

**Apply Zendesk Macro**

> Use Zendesk to apply zendesk macro and walk me through the result in plain English.

**Autocomplete Users**

> Use Zendesk to autocomplete users and walk me through the result in plain English.

**Count Zendesk Organizations**

> Use Zendesk to count zendesk organizations and walk me through the result in plain English.

**Create Automation**

> Create it in Zendesk for me, then confirm the important fields before you finish.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app 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 Zendesk working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a Zendesk app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Zendesk through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Zendesk. | 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 Zendesk actions to the runtime in a format your agent can reliably use. | 452 tools for Zendesk are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Zendesk 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 Zendesk in the browser, and the 452 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

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

### Zendesk 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.

### OAuth finished in the browser but the account is still missing
Try reconnecting Zendesk and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

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

### How do I add Zendesk to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Zendesk skill from ClawHub, then you click Connect in the dashboard to authorize Zendesk. OpenClaw calls the tools from the next message — no config files or API keys to manage.

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

### Why use ClawLink instead of wiring Zendesk up myself?
The alternative to ClawLink is usually manual OAuth app 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 Zendesk working from chat.

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

- [Gleap tools](https://claw-link.dev/openclaw/gleap) — Gleap is an all-in-one customer feedback tool for apps and websites, enabling direct communication with users to build better software by discovering their everyday pain points.
- [OpenClaw Freshdesk integration](https://claw-link.dev/openclaw/freshdesk) — Handle support tickets, contacts, and helpdesk operations
- [Connect Intercom](https://claw-link.dev/openclaw/intercom) — Manage conversations, contacts, companies, and support articles