Automate Zendesk
HumDay reads Zendesk’s own published API description and derives 636 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Zendesk is
Zendesk is a customer support platform built around tickets: requesters, agents, groups, comments, tags and macros, with users, organisations, views and satisfaction ratings.
API host: {subdomain}.{domain}.com
Things people automate with Zendesk
What HumDay can do in Zendesk
304 documented operations change something in Zendesk. The 50 most useful are listed here.
- POSTRecord a New Skip for the Current User
/api/v2/skips - POSTCreate Ticket or Voicemail Ticket
/api/v2/channels/voice/tickets - POSTCreate Ticket from Tweet
/api/v2/channels/twitter/tickets - POSTCreate User
/api/v2/users - POSTCreate Ticket
/api/v2/tickets - POSTCreate Ticket Form
/api/v2/ticket_forms - POSTCreate Task List Template
/api/v2/task_list_templates - POSTCreate Task List
/api/v2/tickets/{ticket_id}/task_lists - POSTRequest User Create
/api/v2/users/request_create - POSTCreate Item
/api/v2/dynamic_content/items - POSTCreate Or Update User
/api/v2/users/create_or_update - PUTRedact Chat Comment
/api/v2/chat_redactions/{ticket_id} - PUTRedact Chat Comment Attachment
/api/v2/chat_file_redactions/{ticket_id} - POSTUpload Files
/api/v2/uploads - POSTCreate User Field
/api/v2/user_fields - PUTRedact Ticket Comment In Agent Workspace
/api/v2/comment_redactions/{ticket_comment_id} - POSTCreate Ticket Field
/api/v2/ticket_fields - POSTCreate Saved Search
/api/v2/saved_searches - POSTCreate Custom Ticket Status
/api/v2/custom_statuses - PUTAdd User Tags
/api/v2/users/{user_id}/tags - POSTCreate Deletion Schedule
/api/v2/deletion_schedules - POSTCreate Ticket Trigger Category
/api/v2/trigger_categories - POSTCreate Ticket Content Pin
/api/v2/ticket_content_pins - POSTCreate Identity
/api/v2/users/{user_id}/identities - POSTCreate Organization Subscription
/api/v2/organization_subscriptions - POSTCreate Group Membership for User
/api/v2/users/{user_id}/group_memberships - POSTCreate Custom Task Item
/api/v2/task_lists/{task_list_id}/task_items - POSTTicket Import
/api/v2/imports/tickets - POSTCreate Organization Membership for User
/api/v2/users/{user_id}/organization_memberships - PATCHCreate or Update Custom Object Record
/api/v2/custom_objects/{custom_object_key}/records - POSTCreate Custom Object Record
/api/v2/custom_objects/{custom_object_key}/records - POSTCreate Many Users
/api/v2/users/create_many - POSTCreate Many Tickets
/api/v2/tickets/create_many - POSTCreate Batch Job for Ticket Trigger Categories
/api/v2/trigger_categories/jobs - POSTCreate Ticket Form Statuses
/api/v2/ticket_forms/{ticket_form_id}/ticket_form_statuses - PUTRedact String in Comment
/api/v2/tickets/{ticket_id}/comments/{ticket_comment_id}/redact - POSTCreate Or Update Many Users
/api/v2/users/create_or_update_many - POSTSuspended Ticket Attachments
/api/v2/suspended_tickets/attachments - POSTCreate Ticket Form Statuses for a Custom Status
/api/v2/custom_statuses/{custom_status_id}/ticket_form_statuses - DELETEDelete User
/api/v2/users/{user_id} - PUTUpdate User
/api/v2/users/{user_id} - PUTMake Comment Private
/api/v2/tickets/{ticket_id}/comments/{ticket_comment_id}/make_private - DELETEDelete Ticket
/api/v2/tickets/{ticket_id} - PUTUpdate Ticket
/api/v2/tickets/{ticket_id} - DELETEDelete Suspended Ticket
/api/v2/suspended_tickets/{id} - PUTUpdate Current User Settings
/api/v2/users/me/settings - PUTUpdate Custom Task List
/api/v2/task_lists/{task_list_id} - DELETEDelete Ticket Permanently
/api/v2/deleted_tickets/{ticket_id} - DELETEDelete Ticket Form
/api/v2/ticket_forms/{ticket_form_id} - PUTUpdate Ticket Form
/api/v2/ticket_forms/{ticket_form_id}
What HumDay can read from Zendesk
These are the operations a schedule or a trigger can watch.
- GETList Ticket Problems
/api/v2/problems - GETList Ticket Form Statuses
/api/v2/ticket_form_statuses - GETList Comments
/api/v2/tickets/{ticket_id}/comments - GETList Email CCs for a Ticket
/api/v2/tickets/{ticket_id}/email_ccs - GETList User CCD Tickets
/api/v2/users/{user_id}/tickets/ccd - GETList User Assigned Tickets
/api/v2/users/{user_id}/tickets/assigned - GETList User Followed Tickets
/api/v2/users/{user_id}/tickets/followed - GETList User Requested Tickets
/api/v2/users/{user_id}/tickets/requested - GETList Ticket Metric Events
/api/v2/incremental/ticket_metric_events - GETList All Skips
/api/v2/skips - GETList Users
/api/v2/users - GETList Search Results
/api/v2/search - GETList Tickets
/api/v2/tickets - GETList Ticket Triggers
/api/v2/triggers - GETList Tickets Fulfilled by a User
/api/v2/routing/requirements/fulfilled - GETList User Fields
/api/v2/user_fields - GETList Ticket Forms
/api/v2/ticket_forms - GETList Deleted Users
/api/v2/deleted_users - GETList All Ticket Audits
/api/v2/ticket_audits - GETList Ticket Fields
/api/v2/ticket_fields - GETList Ticket Metrics
/api/v2/ticket_metrics - GETList Custom Ticket Statuses
/api/v2/custom_statuses - GETList Deleted Tickets
/api/v2/deleted_tickets - GETList User Tags
/api/v2/users/{user_id}/tags - GETList Ticket Skips
/api/v2/users/{user_id}/skips - GETList Suspended Tickets
/api/v2/suspended_tickets - GETList User Groups
/api/v2/users/{user_id}/groups - GETList Ticket Trigger Categories
/api/v2/trigger_categories - GETList Email Notifications
/api/v2/email_notifications - GETList Task List Templates
/api/v2/task_list_templates - GETList Ticket Content Pins
/api/v2/ticket_content_pins - GETList User Requests
/api/v2/users/{user_id}/requests - GETList Sessions for User
/api/v2/users/{user_id}/sessions - GETList Ticket Skips By Ticket
/api/v2/tickets/{ticket_id}/skips - GETList Ticket statuses
/api/v2/channels/twitter/tickets/{comment_id}/statuses - GETList Audits for a Ticket
/api/v2/tickets/{ticket_id}/audits - GETList Identities
/api/v2/users/{user_id}/identities - GETList Monitored X Handles
/api/v2/channels/twitter/monitored_twitter_handles - GETList Brand Agent Memberships By User
/api/v2/users/{user_id}/brand_agents - GETList Followers for a Ticket
/api/v2/tickets/{ticket_id}/followers - GETList Ticket Incidents
/api/v2/tickets/{ticket_id}/incidents - GETList User Organizations
/api/v2/users/{user_id}/organizations - GETShow Task Lists for Ticket
/api/v2/tickets/{ticket_id}/task_lists - GETList Collaborators for a Ticket
/api/v2/tickets/{ticket_id}/collaborators - GETList Group Memberships by User
/api/v2/users/{user_id}/group_memberships - GETList Task Items
/api/v2/task_lists/{task_list_id}/task_items - GETList Conversation log for Ticket
/api/v2/tickets/{ticket_id}/conversation_log - GETSearch Users
/api/v2/users/search - GETList Recent Tickets
/api/v2/tickets/recent - GETList Active Ticket Triggers
/api/v2/triggers/active
How automating Zendesk works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Zendesk account.
- Grant access, then go live. You approve the specific Zendesk operations it may use — and only those.
Automate Zendesk with these
- StackExchange124 operations
- Intercom108 operations
- Twinehealth Fitbit Plus62 operations
- HubSpot Tickets12 operations
- Drchrono263 operations
- Pipedrive196 operations
- SalesLoft Platform118 operations
- Attio90 operations
- Orbit33 operations
- Journy Developer documentation15 operations
- HubSpot Contacts13 operations
- HubSpot Companies12 operations
Categories
Questions about Zendesk automation
- Can HumDay connect to Zendesk?
- Yes. HumDay reads Zendesk's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 636 operations are documented.
- Do I need to write code to automate Zendesk?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Zendesk account.
- What can HumDay do in Zendesk?
- 304 of the 636 documented operations change something in Zendesk, and 332 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Zendesk account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Zendesk is held behind that approval.
Where this came from
The operations above are read from the API description Zendesk publishes themselves at developer.zendesk.com/zendesk/oas.yaml. Descriptions are the provider’s own words, not ours.