Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage Zendesk tickets, users, and support workflows with API integration and automation.
Manage Zendesk tickets, users, and support workflows with API integration and automation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for API credentials and workspace integration.
User needs to interact with Zendesk: create or update tickets, search support history, check user details, or automate support workflows. Agent handles API operations, ticket management, and reporting.
Memory at ~/zendesk/. See memory-template.md for structure. ~/zendesk/ โโโ memory.md # Credentials + preferences + recent context โโโ templates/ # Saved ticket templates and macros โโโ exports/ # Report exports and ticket dumps
TopicFileSetup processsetup.mdMemory templatememory-template.mdAPI operationsapi-reference.mdCommon issuestroubleshooting.md
Credentials from environment variables (ZENDESK_SUBDOMAIN, ZENDESK_EMAIL, ZENDESK_TOKEN) or ~/zendesk/memory.md. # Test auth curl -u "$ZENDESK_EMAIL/token:$ZENDESK_TOKEN" "https://$ZENDESK_SUBDOMAIN.zendesk.com/api/v2/users/me.json"
Always search existing tickets before creating new ones to avoid duplicates. curl -u "$AUTH" "$BASE/search.json?query=type:ticket+subject:issue"
Don't list all tickets. Use views to get relevant subsets. ViewUse Case/views/activeGet available views/views/{id}/ticketsTickets in specific view/tickets/recentRecently updated
When updating, add internal notes explaining changes. Never delete ticket data.
Zendesk limits: 700 requests/minute (Enterprise), 200/minute (others). Add delays for bulk operations.
Before closing, merging, or deleting tickets, confirm with user and summarize what will happen.
Set auth: AUTH="$ZENDESK_EMAIL/token:$ZENDESK_TOKEN" and BASE="https://$ZENDESK_SUBDOMAIN.zendesk.com/api/v2"
curl -X POST "$BASE/tickets.json" -u "$AUTH" -H "Content-Type: application/json" \ -d '{"ticket":{"subject":"Issue","comment":{"body":"Description"},"priority":"normal"}}'
curl -X PUT "$BASE/tickets/$ID.json" -u "$AUTH" -H "Content-Type: application/json" \ -d '{"ticket":{"status":"solved","comment":{"body":"Resolution","public":false}}}'
curl -u "$AUTH" "$BASE/search.json?query=type:ticket+status:open+priority:urgent"
curl -u "$AUTH" "$BASE/users/search.json?query=email:user@example.com"
StatusMeaningNext ActionsnewUnassignedAssign, respondopenBeing workedUpdate, solvependingWaiting on customerFollow up, solveholdWaiting internallyUnhold, updatesolvedResolution providedClose (auto after 4 days)closedFinalReopen creates new ticket
PrioritySLA TargetUse Forurgent1 hourSystem down, revenue impacthigh4 hoursMajor feature brokennormal8 hoursStandard issueslow24 hoursQuestions, minor bugs
Auth format wrong โ Must be email/token:API_TOKEN, not just token Searching with special chars โ URL-encode queries Bulk updates failing โ Check rate limits, add 100ms delay Missing ticket fields โ Some fields require specific plans Pagination ignored โ Results capped at 100, use next_page URL
EndpointData SentPurposehttps://{subdomain}.zendesk.com/api/v2/*Ticket/user dataAll operations No other data is sent externally.
Data that leaves your machine: Ticket content sent to Zendesk API Search queries sent to Zendesk Data that stays local: API credentials in ~/zendesk/memory.md Exported reports in ~/zendesk/exports/ This skill does NOT: Store credentials in plain text outside ~/zendesk/ Send data to any service other than Zendesk Access tickets without explicit user request
By using this skill, ticket and user data is sent to Zendesk's API. Only install if you have authorized Zendesk API access.
Install with clawhub install <slug> if user confirms: api - REST API patterns customer-support - Support best practices csv - Export and analyze ticket data
If useful: clawhub star zendesk Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.