Zendesk Automation via Rube MCP
Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.
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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit zendesk
- If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth
- 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:
ZENDESK_LIST_ZENDESK_TICKETS - List all tickets with pagination [Required]
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:
ZENDESK_SEARCH_ZENDESK_USERS - Find requester/assignee [Prerequisite]
ZENDESK_CREATE_ZENDESK_TICKET - Create a new ticket [Required]
ZENDESK_UPDATE_ZENDESK_TICKET - Update ticket fields [Optional]
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:
ZENDESK_GET_ZENDESK_TICKET_BY_ID - Get current ticket state [Prerequisite]
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:
ZENDESK_SEARCH_ZENDESK_USERS - Search for users [Required]
ZENDESK_CREATE_ZENDESK_USER - Create a new user [Optional]
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:
ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS - List all organizations [Required]
ZENDESK_GET_ZENDESK_ORGANIZATION - Get specific organization [Optional]
ZENDESK_CREATE_ZENDESK_ORGANIZATION - Create organization [Optional]
ZENDESK_UPDATE_ZENDESK_ORGANIZATION - Update organization [Optional]
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) |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---
2name: zendesk-automation
3description: 'Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.'
4metadata:
5 source: https://skillmd.com/skills/sickn33/zendesk-automation
6 aas-risk: critical
7 aas-source: community
8 aas-date-added: '2026-02-27'
9---
10
11# Zendesk Automation via Rube MCP
12
13Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.
14
15## Prerequisites
16
17- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
18- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`
19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
20
21## Setup
22
23**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.
24
25
261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`
283. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth
294. Confirm connection status shows ACTIVE before running any workflows
30
31## Core Workflows
32
33### 1. List and Search Tickets
34
35**When to use**: User wants to view, filter, or search support tickets
36
37**Tool sequence**:
381. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]
392. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]
40
41**Key parameters**:
42- `page`: Page number (1-based)
43- `per_page`: Results per page (max 100)
44- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')
45- `sort_order`: 'asc' or 'desc'
46- `ticket_id`: Ticket ID for single retrieval
47
48**Pitfalls**:
49- LIST uses `page`/`per_page` pagination, NOT offset-based; check `next_page` in response
50- Maximum 100 results per page; iterate with page numbers until `next_page` is null
51- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'
52- Ticket comments and audits are included in GET_BY_ID but not in LIST responses
53
54### 2. Create and Update Tickets
55
56**When to use**: User wants to create new tickets or modify existing ones
57
58**Tool sequence**:
591. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester/assignee [Prerequisite]
602. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]
613. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]
624. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]
63
64**Key parameters**:
65- `subject`: Ticket subject line
66- `description`: Ticket body (for creation; becomes first comment)
67- `priority`: 'urgent', 'high', 'normal', 'low'
68- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'
69- `type`: 'problem', 'incident', 'question', 'task'
70- `assignee_id`: Agent user ID to assign
71- `requester_id`: Requester user ID
72- `tags`: Array of tag strings
73- `ticket_id`: Ticket ID (for update/delete)
74
75**Pitfalls**:
76- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them
77- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts
78- DELETE is permanent and irreversible; tickets cannot be recovered
79- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation
80- Closed tickets cannot be updated; create a follow-up ticket instead
81
82### 3. Reply to Tickets
83
84**When to use**: User wants to add comments or replies to tickets
85
86**Tool sequence**:
871. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]
882. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply/comment [Required]
89
90**Key parameters**:
91- `ticket_id`: Ticket ID to reply to
92- `body`: Reply text content
93- `public`: Boolean; true for public reply, false for internal note
94- `author_id`: Author user ID (defaults to authenticated user)
95
96**Pitfalls**:
97- Set `public: false` for internal notes visible only to agents
98- Default is public reply which sends email to requester
99- HTML is supported in body text
100- Replying can also update ticket status simultaneously
101
102### 4. Manage Users
103
104**When to use**: User wants to find or create Zendesk users (agents, end-users)
105
106**Tool sequence**:
1071. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]
1082. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]
1093. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]
110
111**Key parameters**:
112- `query`: Search string (matches name, email, phone, etc.)
113- `name`: User's full name (required for creation)
114- `email`: User's email address
115- `role`: 'end-user', 'agent', or 'admin'
116- `verified`: Whether email is verified
117
118**Pitfalls**:
119- User search is fuzzy; may return partial matches
120- Creating a user with an existing email returns the existing user (upsert behavior)
121- Agent and admin roles may require specific plan features
122
123### 5. Manage Organizations
124
125**When to use**: User wants to list, create, or manage organizations
126
127**Tool sequence**:
1281. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]
1292. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]
1303. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]
1314. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]
1325. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]
133
134**Key parameters**:
135- `name`: Organization name (unique, required for creation)
136- `organization_id`: Organization ID for get/update
137- `details`: Organization details text
138- `notes`: Internal notes
139- `domain_names`: Array of associated domains
140- `tags`: Array of tag strings
141
142**Pitfalls**:
143- Organization names must be unique; duplicate names cause creation errors
144- Tags on UPDATE REPLACE existing tags (same behavior as tickets)
145- Domain names can be used for automatic user association
146
147## Common Patterns
148
149### Pagination
150
151**List endpoints**:
152- Use `page` (1-based) and `per_page` (max 100)
153- Check `next_page` URL in response; null means last page
154- `count` field gives total results
155
156### Ticket Lifecycle
157
158```
159new -> open -> pending -> solved -> closed
160 | ^
161 v |
162 hold --------+
163```
164
165- `new`: Unassigned ticket
166- `open`: Assigned, being worked on
167- `pending`: Waiting for customer response
168- `hold`: Waiting for internal action
169- `solved`: Resolved, can be reopened
170- `closed`: Permanently closed, cannot be modified
171
172### User Search for Assignment
173
174```
1751. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)
1762. Extract user ID from results
1773. Use user ID as assignee_id in ticket creation/update
178```
179
180## Known Pitfalls
181
182**Tags Behavior**:
183- Tags on update REPLACE all existing tags
184- Always fetch current tags first and merge before updating
185- Tags are lowercase, no spaces (use underscores)
186
187**Safe Updates**:
188- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts
189- Returns 409 if ticket was modified since the stamp
190
191**Deletion**:
192- Ticket deletion is permanent and irreversible
193- Consider setting status to 'closed' instead of deleting
194- Deleted tickets cannot be recovered via API
195
196**Rate Limits**:
197- Default: 400 requests per minute
198- Varies by plan tier
199- 429 responses include Retry-After header
200
201## Quick Reference
202
203| Task | Tool Slug | Key Params |
204|------|-----------|------------|
205| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |
206| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |
207| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |
208| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |
209| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |
210| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |
211| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |
212| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |
213| My profile | ZENDESK_GET_ABOUT_ME | (none) |
214| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |
215| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |
216| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |
217| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |
218| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |
219
220## When to Use
221This skill is applicable to execute the workflow or actions described in the overview.
222
223## Limitations
224- Use this skill only when the task clearly matches the scope described above.
225- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
226- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.