Connect Zendesk to your Gumloop workflows so you can search, create, and manage tickets, users, views, triggers, automations, and more - all with natural language prompts. Skip the API docs and handle day-to-day support tasks in seconds.
Work with every major Zendesk object using 30+ purpose-built tools covering tickets, users, triggers, automations, macros, tags, and views.

​
What is Zendesk MCP?

When you create a Zendesk MCP node, Gumloop automatically builds a customized node that understands the Zendesk API. Simply describe what you want in plain English and the node handles authentication, endpoints, and formatting for you. Talk to Zendesk like a teammate instead of writing code.

​
What Can It Do for You?

  • Instantly search, list, create, or update tickets without leaving Gumloop
  • Look up users, groups, views, and macros to power routing or reporting workflows
  • Manage triggers, automations, and tags to keep your support instance organized
  • Pull complete comment histories for analytics, sentiment analysis, or hand-off documentation

​
Available Tools

ToolWhat It DoesExample Use
List TicketsSearch or list tickets with advanced filters, pagination, and sorting”List tickets created after 2024-01-01 with status ‘open’ and return id, subject, requester_id, and created_at”
Get TicketRetrieve a single ticket with collaborators, followers, CCs, and comments”Get ticket with subject ‘Billing issue - duplicate charge’ and return subject, status, priority, and last_comment”
Create TicketCreate a new ticket with custom fields, collaborators, and attachments”Create a ticket with subject ‘Login not working’, requester_email ‘john.doe@customer.com’, priority ‘high’, and return id and url”
Update TicketUpdate fields on an existing ticket and optionally add comments”Update ticket ‘Password reset request’ set status ‘solved’, add public comment ‘Issue resolved - password reset link sent’, and return status and updated_at”
Merge TicketsMerge multiple tickets into one target ticket”Merge duplicate tickets about ‘shipping delay order #1234’ into the original ticket and return resulting_ticket_id”
Create CommentAdd a public or private comment to a ticket”Add a public comment ‘We’re investigating this issue and will update you shortly’ to ticket ‘App crashes on startup’ and return comment_id”
List CommentsList all comments for a ticket with user and attachment info”List comments for ticket ‘Refund request #5678’ and return author_id, body_text, created_at”
List Ticket FieldsGet schema and options for ticket fields”List ticket fields and return id, title, and type”
List Ticket FormsRetrieve all ticket forms with their required fields”List ticket forms and return id, name, and active”
List UsersList agents or end-users with filters”List users with role ‘agent’ and return id, name, email”
Get UserGet detailed information for a single user”Get user with email ‘support.agent@company.com’ and return name, role, organization_id”
Search UsersSearch users by email, name, phone, or notes”Search users where email contains ‘acme.com’ and return id, name, email”
List GroupsList agent groups for assignments”List groups and return id and name”
Get GroupGet details for a specific group”Get group ‘Tier 2 Support’ and return name, created_at, member_count”
List TagsList all tags ordered by popularity in last 60 days”List tags and return name and count”
Search TagsAutocomplete tags by name prefix”Search tags starting with ‘priority_’ and return name”
Add TagsAdd tags to tickets, organizations, or users”Add tags [‘vip’, ‘enterprise’] to ticket ‘Account upgrade request’ “
Remove TagsRemove tags from tickets, organizations, or users”Remove tag ‘urgent’ from ticket ‘Feature request - dark mode‘“
List ViewsList shared and personal views available to the user”List views and return id, title, and active”
Get ViewGet detailed information for a view”Get view ‘Unassigned Tickets’ and return title and conditions”
Get Tickets In ViewRetrieve tickets from a specific view with pagination”Get tickets in view ‘My Open Tickets’ page 1 return id, subject, status”
List AutomationsList all automations with filters and usage stats”List automations and return id, title, active”
Search AutomationsSearch automations by title”Search automations title contains ‘auto-reply’ and return id and title”
Get AutomationGet detailed automation configuration”Get automation ‘Close inactive tickets after 7 days’ and return title and conditions”
List TriggersList all ticket triggers with filters and usage stats”List triggers and return id, title, active”
Search TriggersSearch triggers by title”Search triggers title contains ‘escalation’ and return id and title”
Get TriggerGet detailed trigger configuration”Get trigger ‘Notify manager on high priority’ and return title, conditions, actions”
List Trigger CategoriesList categories that organize triggers”List trigger categories and return id and name”
List MacrosList shared and personal macros with filters and stats”List macros and return id, title, usage_30d”
Search MacrosSearch macros by title”Search macros title contains ‘refund’ and return id and title”
Get MacroGet detailed macro information”Get macro ‘Standard refund response’ and return title and actions”

​
How to Use

1

Create Your Zendesk MCP Node

Go to your node library, search for Zendesk, and click “Create a node with AI”
2

Add Your Prompt

Drag the Zendesk node onto your canvas and type a clear, focused prompt using one of the tools above.
3

Test Your Node

Run the node to verify the output. If needed, tweak filters or requested fields for the perfect result.
4

Save and Reuse

Save the customized Zendesk node to your library and reuse it in any workflow.

​
Example Prompts

With 30 available tools, these examples showcase common use cases. Experiment with natural language to discover more possibilities. Ticket Lookup: 
List tickets where priority is high and status is open created after 2025-05-01, return id, subject, requester_id, and created_at
User Search: 
Search users where name contains "Jordan Lee" and return id, email, and role
Create a New Ticket: 
Create a ticket with subject "Cannot reset password", description "User receives error 500", requester_email "pat@globex.com", priority urgent, return id and status
Add a Comment: 
Add a private comment "Escalated to engineering, awaiting update" to ticket 789012 and return comment_id and created_at
View Reporting: 
Get tickets in view 223344 page 1 sorted by created_at desc and return id, subject, status
Tag Management: 
Add tags ["vip_customer"] to the provided user email and return updated_tags
Trigger Review: 
Search triggers title contains "SLA breach" return id, title, and active
Start with a single, crystal-clear action such as “List tickets status open” before adding filters. Simple prompts return faster and make debugging easier.

​
Troubleshooting

If your Zendesk node isn’t delivering the expected results, follow these tips.

​
Keep Prompts Simple and Specific

  • Good: “List tickets status open return id and subject”
  • Bad: “List open tickets, then find their requesters and output the summary”
While this prompt might work, it’s more efficient to break it into separate nodes. Zendesk MCP works best with focused, single-action prompts.

​
Match What Zendesk Can Do

  • Good: “Get Trigger ID return title and actions”
  • Bad: “Translate trigger actions to French and post them to Slack”
Zendesk MCP focuses on support data. For translation, connect it to an Ask AI node, and for Slack posting, add a Slack Message Sender node in your workflow.

​
Break Complex Tasks Into Steps

Instead of trying to do everything in one prompt (which might cause timeouts or errors): 
List tickets, update their status to pending, and send a summary email to the requester
Break this into smaller, focused nodes that each handle one task:
1

Step 1: List Tickets

List tickets status open created_before 2025-06-01 return id, requester_id
2

Step 2: Update Tickets

Update ticket ticket_id set status pending
3

Step 3: Email Requesters using the 'Gmail Sender' node

Send email via Gmail Sender using requester_id with subject “Ticket Update” and body “Your ticket is now pending”
In your workflow, connect these nodes sequentially. The ticket IDs output from Step 1 feed into Step 2, and the requester IDs from Step 1 feed into Step 3.

​
Focus on Data Retrieval

Zendesk MCP is great at getting information from Zendesk. For analysis or content creation, pair it with other nodes. Example:
  • Good prompt: “List comments for a given Ticket URL return author_id and body_text”
  • Bad prompt: “Analyze sentiment of comments and write a summary paragraph”
Use the Ask AI node to run sentiment analysis or summarization once Zendesk provides the raw comment data.

​
Troubleshooting Node Creation

​
Need More Help?