AGENT SKILL

zendesk-automation

Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
zendesk-automation
category
customer-support
requires
{ "mcp": [ "rube" ] }
description
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.

03 SKILL.md 正文

Zendesk Automation via Rube MCP

Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/zendesk

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Zendesk connection via RUBE_MANAGE_CONNECTIONS with toolkit zendesk
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit zendesk
  3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth
  4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. List and Search Tickets

When to use: User wants to view, filter, or search support tickets

Tool sequence:

  1. ZENDESK_LIST_ZENDESK_TICKETS - List all tickets with pagination [Required]
  2. ZENDESK_GET_ZENDESK_TICKET_BY_ID - Get specific ticket details [Optional]

Key parameters:

  • page: Page number (1-based)
  • per_page: Results per page (max 100)
  • sort_by: Sort field ('created_at', 'updated_at', 'priority', 'status')
  • sort_order: 'asc' or 'desc'
  • ticket_id: Ticket ID for single retrieval

Pitfalls:

  • LIST uses page/per_page pagination, NOT offset-based; check next_page in response
  • Maximum 100 results per page; iterate with page numbers until next_page is null
  • Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'
  • Ticket comments and audits are included in GET_BY_ID but not in LIST responses

2. Create and Update Tickets

When to use: User wants to create new tickets or modify existing ones

Tool sequence:

  1. ZENDESK_SEARCH_ZENDESK_USERS - Find requester/assignee [Prerequisite]
  2. ZENDESK_CREATE_ZENDESK_TICKET - Create a new ticket [Required]
  3. ZENDESK_UPDATE_ZENDESK_TICKET - Update ticket fields [Optional]
  4. ZENDESK_DELETE_ZENDESK_TICKET - Delete a ticket [Optional]

Key parameters:

  • subject: Ticket subject line
  • description: Ticket body (for creation; becomes first comment)
  • priority: 'urgent', 'high', 'normal', 'low'
  • status: 'new', 'open', 'pending', 'hold', 'solved', 'closed'
  • type: 'problem', 'incident', 'question', 'task'
  • assignee_id: Agent user ID to assign
  • requester_id: Requester user ID
  • tags: Array of tag strings
  • ticket_id: Ticket ID (for update/delete)

Pitfalls:

  • Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them
  • Use safe_update with updated_stamp to prevent concurrent modification conflicts
  • DELETE is permanent and irreversible; tickets cannot be recovered
  • description is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation
  • Closed tickets cannot be updated; create a follow-up ticket instead

3. Reply to Tickets

When to use: User wants to add comments or replies to tickets

Tool sequence:

  1. ZENDESK_GET_ZENDESK_TICKET_BY_ID - Get current ticket state [Prerequisite]
  2. ZENDESK_REPLY_ZENDESK_TICKET - Add a reply/comment [Required]

Key parameters:

  • ticket_id: Ticket ID to reply to
  • body: Reply text content
  • public: Boolean; true for public reply, false for internal note
  • author_id: Author user ID (defaults to authenticated user)

Pitfalls:

  • Set public: false for internal notes visible only to agents
  • Default is public reply which sends email to requester
  • HTML is supported in body text
  • Replying can also update ticket status simultaneously

4. Manage Users

When to use: User wants to find or create Zendesk users (agents, end-users)

Tool sequence:

  1. ZENDESK_SEARCH_ZENDESK_USERS - Search for users [Required]
  2. ZENDESK_CREATE_ZENDESK_USER - Create a new user [Optional]
  3. ZENDESK_GET_ABOUT_ME - Get authenticated user info [Optional]

Key parameters:

  • query: Search string (matches name, email, phone, etc.)
  • name: User's full name (required for creation)
  • email: User's email address
  • role: 'end-user', 'agent', or 'admin'
  • verified: Whether email is verified

Pitfalls:

  • User search is fuzzy; may return partial matches
  • Creating a user with an existing email returns the existing user (upsert behavior)
  • Agent and admin roles may require specific plan features

5. Manage Organizations

When to use: User wants to list, create, or manage organizations

Tool sequence:

  1. ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS - List all organizations [Required]
  2. ZENDESK_GET_ZENDESK_ORGANIZATION - Get specific organization [Optional]
  3. ZENDESK_CREATE_ZENDESK_ORGANIZATION - Create organization [Optional]
  4. ZENDESK_UPDATE_ZENDESK_ORGANIZATION - Update organization [Optional]
  5. ZENDESK_COUNT_ZENDESK_ORGANIZATIONS - Get total count [Optional]

Key parameters:

  • name: Organization name (unique, required for creation)
  • organization_id: Organization ID for get/update
  • details: Organization details text
  • notes: Internal notes
  • domain_names: Array of associated domains
  • tags: Array of tag strings

Pitfalls:

  • Organization names must be unique; duplicate names cause creation errors
  • Tags on UPDATE REPLACE existing tags (same behavior as tickets)
  • Domain names can be used for automatic user association

Common Patterns

Pagination

List endpoints:

  • Use page (1-based) and per_page (max 100)
  • Check next_page URL in response; null means last page
  • count field gives total results

Ticket Lifecycle

new -> open -> pending -> solved -> closed
                  |          ^
                  v          |
                hold --------+
  • new: Unassigned ticket
  • open: Assigned, being worked on
  • pending: Waiting for customer response
  • hold: Waiting for internal action
  • solved: Resolved, can be reopened
  • closed: Permanently closed, cannot be modified

User Search for Assignment

1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)
2. Extract user ID from results
3. Use user ID as assignee_id in ticket creation/update

Known Pitfalls

Tags Behavior:

  • Tags on update REPLACE all existing tags
  • Always fetch current tags first and merge before updating
  • Tags are lowercase, no spaces (use underscores)

Safe Updates:

  • Use safe_update: true with updated_stamp (ISO 8601) to prevent conflicts
  • Returns 409 if ticket was modified since the stamp

Deletion:

  • Ticket deletion is permanent and irreversible
  • Consider setting status to 'closed' instead of deleting
  • Deleted tickets cannot be recovered via API

Rate Limits:

  • Default: 400 requests per minute
  • Varies by plan tier
  • 429 responses include Retry-After header

Quick Reference

Task Tool Slug Key Params
List tickets ZENDESK_LIST_ZENDESK_TICKETS page, per_page, sort_by
Get ticket ZENDESK_GET_ZENDESK_TICKET_BY_ID ticket_id
Create ticket ZENDESK_CREATE_ZENDESK_TICKET subject, description, priority
Update ticket ZENDESK_UPDATE_ZENDESK_TICKET ticket_id, status, tags
Reply to ticket ZENDESK_REPLY_ZENDESK_TICKET ticket_id, body, public
Delete ticket ZENDESK_DELETE_ZENDESK_TICKET ticket_id
Search users ZENDESK_SEARCH_ZENDESK_USERS query
Create user ZENDESK_CREATE_ZENDESK_USER name, email
My profile ZENDESK_GET_ABOUT_ME (none)
List orgs ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS page, per_page
Get org ZENDESK_GET_ZENDESK_ORGANIZATION organization_id
Create org ZENDESK_CREATE_ZENDESK_ORGANIZATION name
Update org ZENDESK_UPDATE_ZENDESK_ORGANIZATION organization_id, name
Count orgs ZENDESK_COUNT_ZENDESK_ORGANIZATIONS (none)

Powered by Composio

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1