# How to connect Freshdesk to OpenClaw (paste one key, 178 tools)

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

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

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

## Setup

It takes three steps to connect OpenClaw to Freshdesk.

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

Verify the connection by asking OpenClaw:

> Use Freshdesk to add note to ticket 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 Freshdesk is connected in the dashboard, that agent calls the same 178 Freshdesk 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).

## Freshdesk MCP for OpenClaw

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

## What the OpenClaw Freshdesk integration can do

178 Freshdesk 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 178.

### 30 of 178 Freshdesk tools for OpenClaw

| Tool | What it does |
|---|---|
| **Add note to ticket** `freshdesk_add_note_to_ticket` | Add a private or public note to a ticket |
| **Add ticket user access** `freshdesk_add_ticket_user_access` | Add agent access to a specific ticket |
| **Add watcher** `freshdesk_add_watcher` | Add the authenticated user as a watcher to a ticket |
| **Bulk update tickets** `freshdesk_bulk_update_tickets` | Update multiple tickets simultaneously in bulk |
| **Create admin group** `freshdesk_create_admin_group` | Create a new admin-level support agent group |
| **Create agents** `freshdesk_create_agents` | Create multiple agents in Freshdesk |
| **Create canned response** `freshdesk_create_canned_response` | Create a new canned response in Freshdesk |
| **Create companies** `freshdesk_create_companies` | Create a new company in Freshdesk |
| **Create contact** `freshdesk_create_contact` | Create a new contact in Freshdesk |
| **Currently authenticated agent** `freshdesk_currently_authenticated_agent` | Retrieve profile information for the currently authenticated agent |
| **Get account** `freshdesk_get_account` | View Freshdesk account information |
| **Get agent** `freshdesk_get_agent` | Retrieve detailed information about a specific agent by ID |
| **Get agent availability** `freshdesk_get_agent_availability` | Retrieve availability information for a specific agent |
| **Get agents** `freshdesk_get_agents` | Search for agents using autocomplete functionality in Freshdesk |
| **Get business hours** `freshdesk_get_business_hours` | Retrieves all business hours configurations from Freshdesk |
| **Get canned response folders** `freshdesk_get_canned_response_folders` | Retrieve all canned response folders from Freshdesk |
| **Get companies** `freshdesk_get_companies` | Retrieve all companies from a Freshdesk account with pagination support |
| **Get company** `freshdesk_get_company` | Retrieve detailed information about a specific company by ID |
| **Get company fields** `freshdesk_get_company_fields` | Retrieve all company fields configured in Freshdesk |
| **Get contact** `freshdesk_get_contact` | Retrieve detailed information about a specific contact by ID |
| **Get contact fields** `freshdesk_get_contact_fields` | Retrieve all contact fields configured in Freshdesk |
| **Get contacts** `freshdesk_get_contacts` | Retrieve all contacts from a Freshdesk account |
| **Get discussion category** `freshdesk_get_discussion_category` | View details of a specific forum category in Freshdesk |
| **Get discussion topic** `freshdesk_get_discussion_topic` | Retrieve detailed information about a specific discussion topic by ID |
| **Get email mailbox** `freshdesk_get_email_mailbox` | Retrieve detailed information about a specific email mailbox by ID |
| **Get folder responses** `freshdesk_get_folder_responses` | Retrieve all canned responses within a specific folder in Freshdesk |
| **Get imported contacts** `freshdesk_get_imported_contacts` | Retrieve details of all contact import operations in Freshdesk |
| **Get job** `freshdesk_get_job` | View the status of a bulk job operation |
| **Get scenario automations json** `freshdesk_get_scenario_automations_json` | List all scenario-based automations in Freshdesk |
| **Get search** `freshdesk_get_search` | Search and filter tickets in Freshdesk using flexible query syntax |

## Example prompts

**Add Note To Ticket**

> Use Freshdesk to add note to ticket and walk me through the result in plain English.

**Add Ticket User Access**

> Use Freshdesk to add ticket user access and walk me through the result in plain English.

**Add Watcher**

> Use Freshdesk to add watcher and walk me through the result in plain English.

**Bulk Update Tickets**

> Use Freshdesk to bulk update tickets 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 Freshdesk working from chat.

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

## ClawLink vs. Composio

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

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

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

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

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

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

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

- [Zendesk](https://claw-link.dev/openclaw/zendesk) — Manage support tickets, macros, users, and organizations
- [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.
- [Intercom](https://claw-link.dev/openclaw/intercom) — Manage conversations, contacts, companies, and support articles