Zendesk's API is well-documented and relatively approachable. Connecting it to OpenClaw means your support team can get queue snapshots, ticket details, and customer histories directly in Slack.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Zendesk — it's considerably more involved.
Connecting OpenClaw with Zendesk: Step by Step
Step 1: Create a Zendesk API Token
Go to Zendesk Admin → Apps & Integrations → APIs → Zendesk API and enable token access. Generate a token. Authentication uses HTTP Basic with your agent email address and the token as the password (formatted as email/token:your_token). Your API base is https://{your-subdomain}.zendesk.com/api/v2.
Step 2: Use the Ticket Search Endpoint
The /api/v2/search.json?query=... endpoint supports Zendesk's search syntax — filter by status, priority, assignee, requester, and more. This is your primary tool for queue queries. For individual ticket details, /api/v2/tickets/{id} gives you the full record including comments.
Step 3: Build the Proxy and Skill File
Build your proxy around search and ticket detail endpoints. Write ~/.openclaw/skills/zendesk.md with your SLA targets, common status filter patterns, and agent email-to-name mappings so Claude can present results naturally.
Challenges and Caveats
Rate Limits Apply to All Plans
Zendesk API rate limits are 700 requests per minute for most plans (lower for legacy plans). If your integration is serving a busy support team with many concurrent Slack queries, monitor your usage.
SLA Data Requires the SLA API
SLA policy breach times are in a separate part of the API (/api/v2/ticket_metrics) — the main ticket endpoint doesn't include SLA timestamps by default. Your proxy will need an extra call for SLA-related queries.
Skip All of This — Use Cody Instead
Cody has Zendesk integration built in. Get queue snapshots and ticket context in Slack without API tokens or proxy setup.
Related Guides
- Connecting OpenClaw with Intercom: A Practical Guide
- Connecting OpenClaw with Freshdesk: A Practical Guide
- Connecting OpenClaw with Hubspot: A Practical Guide
Need the model-flexible version? See: How to Connect Zendesk to OpenClaw: Setup, Models, and Workflow Guide.