- Category: crm
- Auth: OAUTH2
- Composio-managed OAuth available? Yes
- Tools: 457
- Triggers: 2
- Slug:
ZENDESK - Version: 20261101_00
Frequently Asked Questions
How do I set up custom OAuth credentials for Zendesk?
How do I set up custom OAuth credentials for Zendesk?
Tools
Apply Zendesk Macro Preview
Apply Zendesk Macro Preview
ZENDESK_APPLY_ZENDESK_MACROPreview how a Zendesk macro would affect a ticket without actually applying it. Returns the ticket object as it would appear after the macro is applied, showing any changes to fields, comments, status, or other properties. Use this action to review macro changes before applying them to ensure the outcome is as expected.Input Parameters
Output
Autocomplete Problems
Autocomplete Problems
Autocomplete Users
Autocomplete Users
ZENDESK_AUTOCOMPLETE_USERSFind Zendesk users using autocomplete by name prefix, phone, or lookup relationship, with optional filters. Name or phone searches cannot be combined with lookup relationship parameters.Input Parameters
Output
Check Host Mapping Validity for Existing Brand
Check Host Mapping Validity for Existing Brand
ZENDESK_CHECK_HOST_MAPPING_VALIDITY_FOR_EXISTING_BRANDCheck the host mapping validity for an existing brand in Zendesk. Returns the current CNAME record, expected CNAME values, validity status, and the reason for validity or invalidity. Use this action when you need to verify that DNS records are correctly configured for an existing brand that has already been created in Zendesk. This action requires a brand ID rather than subdomain/host_mapping parameters.Input Parameters
Output
Count Deleted Users
Count Deleted Users
Count User CCD Tickets
Count User CCD Tickets
ZENDESK_COUNT_USER_CCD_TICKETSCount tickets where the specified user is CCD (carbon copy distribution). Returns an approximate count of tickets where the user appears in the CCD field. Use when you need to know how many tickets a user is copied on for reporting or operational purposes.Input Parameters
Output
Count Custom Object Records
Count Custom Object Records
ZENDESK_COUNT_ZENDESK_CUSTOM_OBJECT_RECORDSCount the number of records in a specific Zendesk custom object. Use when you need to determine the total number of records for a custom object type, which is useful for reporting, capacity planning, or validation before creating new records. This is a read-only, idempotent operation. Example use cases: - Check if a custom object has records before deleting - Get record count for reporting dashboards - Verify capacity before bulk operationsInput Parameters
Output
Count Zendesk Organizations
Count Zendesk Organizations
ZENDESK_COUNT_ZENDESK_ORGANIZATIONSCount the number of organizations in Zendesk. Returns an approximate count of organizations with the timestamp of when the count was last calculated. This is a read-only, idempotent operation. Use when you need to know the total number of organizations for reporting, capacity planning, or operational purposes. For detailed per-organization information, use ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS instead.Output
Create Access Rule
Create Access Rule
ZENDESK_CREATE_ACCESS_RULECreate an access rule for a custom object in Zendesk. Access rules control which users can view or modify custom object records based on conditions. Use when you need to set up data access policies for custom objects, such as limiting access to records created by the current user or records assigned to specific groups. Returns the created access rule with its ID, title, description, conditions, and timestamps.Input Parameters
Output
Install Zendesk App
Install Zendesk App
ZENDESK_CREATE_APPS_INSTALLATIONInstall a Zendesk app in the account. Use when you need to add an app from the Zendesk marketplace or a private app to your Zendesk instance. You must provide the app_id; settings are optional for apps that have defaults or no configurable settings. This action is irreversible once installed.Input Parameters
true for most apps). Pass True or False to override that default explicitly.Output
Send Notification to App
Send Notification to App
ZENDESK_CREATE_APPS_NOTIFYSend a notification to currently open instances of a Zendesk app. Use when you need to push real-time notifications or data to a Zendesk app that is currently open in an agent’s interface. The notification triggers an event in the app, which can then respond with custom behavior (e.g., display a popup, update UI, trigger a workflow). Only works with apps that are currently open in the Zendesk interface.Input Parameters
Output
Create Automation
Create Automation
ZENDESK_CREATE_AUTOMATIONCreate a new automation in Zendesk. Automations are business rules that automatically perform actions on tickets when certain conditions are met. Automations run server-side and don’t require user interaction. Use this action when you need to: - Automatically assign tickets based on conditions - Change ticket priority/status based on rules - Add tags to tickets matching certain criteria - Notify agents or teams based on ticket properties - Implement escalation workflows Note: Automations must have at least one condition that is time-based (like created_at, updated_at) OR check one of: status, type, group_id, assignee_id, or requester_id.Input Parameters
{"all": [], "any": []} to Zendesk and fail server-side.Output
Create Bookmark
Create Bookmark
ZENDESK_CREATE_BOOKMARKCreate a bookmark for a ticket in Zendesk. Bookmarks allow you to save references to tickets for quick access. Use this action when you need to: - Save a ticket for later reference - Mark an important ticket for quick access - Create a watchlist-like functionality for specific ticketsInput Parameters
Output
Redact Zendesk Comment
Redact Zendesk Comment
ZENDESK_CREATE_COMMENT_REDACTIONRedact specified text from a Zendesk ticket comment using the Agent Workspace method. Redaction is irreversible; Agent Workspace and appropriate permissions are required, and comments on closed tickets cannot be redacted.Input Parameters
Output
Create Custom Object Bulk Job
Create Custom Object Bulk Job
ZENDESK_CREATE_CUSTOM_OBJECT_BULK_JOBSubmit a bulk job to create, update, delete, or upsert Zendesk custom object records. Delete items must be objects containing an id or name; the response may include a job ID for tracking progress.Input Parameters
Output
Create Custom Object Record
Create Custom Object Record
ZENDESK_CREATE_CUSTOM_OBJECT_RECORDCreate a record for a Zendesk custom object and return its generated ID and available record fields, including timestamps when provided.Input Parameters
Output
Create Custom Object Record Attachment
Create Custom Object Record Attachment
ZENDESK_CREATE_CUSTOM_OBJECT_RECORD_ATTACHMENTCreate an attachment for a Zendesk custom object record by uploading a file as multipart form data; the response may include attachment details and malware scan status. Accepts an uploaded file reference or a data or permitted local file URL, but rejects remote file links.Input Parameters
Output
Create Custom Ticket Status
Create Custom Ticket Status
ZENDESK_CREATE_CUSTOM_STATUSESCreate a new custom ticket status in Zendesk. Custom statuses allow agents to define more granular ticket states beyond the default status categories. Use when you need to add custom ticket workflow states to better reflect your support process. Both agent_label, status_category, end_user_label, and description are required. The status category determines which lifecycle phase the custom status belongs to.Input Parameters
Output
Create Deletion Schedule
Create Deletion Schedule
ZENDESK_CREATE_DELETION_SCHEDULECreate a Zendesk deletion schedule for records matching specified conditions, for retention or cleanup. The schedule is active by default, and its target object type cannot be changed after creation.Input Parameters
Output
Create Zendesk Dynamic Content Item
Create Zendesk Dynamic Content Item
ZENDESK_CREATE_DYNAMIC_CONTENT_ITEMSCreate a new dynamic content item with locale variants in Zendesk. Dynamic content items enable localized content for ticket fields, macros, and other text-based content. Use when setting up multilingual support or creating template content that varies by user locale. The item’s name cannot be changed after creation. Ensure the name is descriptive and follows your naming conventions.Input Parameters
Output
Create Zendesk Dynamic Content Item Variant
Create Zendesk Dynamic Content Item Variant
ZENDESK_CREATE_DYNAMIC_CONTENT_ITEMS_VARIANTSCreate a new locale variant for an existing dynamic content item in Zendesk. Use when you need to add support for a new locale to an existing dynamic content item. Note: You can only create one variant per locale per dynamic content item. Use the update action to modify existing variants.Input Parameters
Output
Create End User Identity
Create End User Identity
ZENDESK_CREATE_END_USER_IDENTITYAdd an identity (email or phone) to an end user’s profile in Zendesk. Use when you need to link a new email address or phone number to an existing end user account.Input Parameters
Output
Create Zendesk Group Membership
Create Zendesk Group Membership
ZENDESK_CREATE_GROUP_MEMBERSHIPSCreate a group membership in Zendesk, assigning an agent to a group. Use when you need to add an agent to a specific group for ticket routing, permissions, or team organization. The user_id and group_id are both required parameters. Note: The user must exist and have appropriate permissions to be assigned to groups. The group must also exist.Input Parameters
Output
Bulk Import Tickets
Bulk Import Tickets
ZENDESK_CREATE_IMPORTS_TICKETS_CREATE_MANYBulk import tickets into Zendesk by posting up to 100 ticket objects at a time. Use when migrating tickets from another system or creating multiple tickets in a single API call. The operation returns a job_status payload; the initial status is typically ‘queued’ or ‘completed’ for small batches. This action is useful for data migration, test data setup, and bulk ticket creation workflows.Input Parameters
Output
Create Many Dynamic Content Variants
Create Many Dynamic Content Variants
ZENDESK_CREATE_MANY_DYNAMIC_CONTENT_ITEMS_VARIANTSCreate multiple locale variants for an existing Zendesk dynamic content item in one request, supplying localized content and active status. The default-variant flag is not sent.Input Parameters
Output
Create Many Zendesk Tickets
Create Many Zendesk Tickets
ZENDESK_CREATE_MANY_TICKETSCreate many tickets in Zendesk in a single request. Accepts an array of up to 100 ticket objects. The operation is handled asynchronously — a background job is queued and you receive a job_status payload with an initial status of ‘queued’ or ‘working’. Poll the job_status URL or use ZENDESK_GET_APPS_JOB_STATUS to check for completion and view per-ticket results. Use when creating multiple tickets at once or seeding test data. This action is irreversible — tickets created cannot be easily undone once the job completes. Ensure the tickets list is accurate before submitting.Input Parameters
Output
Create Many Zendesk Users
Create Many Zendesk Users
ZENDESK_CREATE_MANY_USERSCreate many users in Zendesk in a single request. Accepts up to 100 user objects. The operation is handled asynchronously — a background job is queued and you receive a job_status payload with an initial status of ‘queued’ or ‘working’. Poll the job_status URL or use ZENDESK_GET_APPS_JOB_STATUS to check for completion and view per-user results. Use when onboarding multiple users at once or seeding test data. Note: This action is idempotent — re-running with the same external_ids may update existing users depending on Zendesk configuration.Input Parameters
Output
Create Object Trigger
Create Object Trigger
ZENDESK_CREATE_OBJECT_TRIGGERCreate a trigger for a Zendesk custom object, defining conditions and actions for automated workflows on its records.Input Parameters
Output
Create Organization Field
Create Organization Field
ZENDESK_CREATE_ORGANIZATION_FIELDCreate a custom organization field in Zendesk. Use when you need to add a new custom field type (such as text, dropdown, checkbox, date, etc.) to track additional organization attributes. The field key must be unique and can only contain letters, numbers, and underscores.Input Parameters
Output
Create Organization Membership
Create Organization Membership
ZENDESK_CREATE_ORGANIZATION_MEMBERSHIPSCreate an organization membership in Zendesk by assigning a user to an organization. By default, the request marks the membership as the user’s default organization; this can be changed.Input Parameters
Output
Create Many Organization Memberships
Create Many Organization Memberships
ZENDESK_CREATE_ORGANIZATION_MEMBERSHIPS_CREATE_MANYCreate multiple organization memberships in Zendesk by posting up to 100 membership objects at a time. Each membership links a user to an organization. Use when onboarding multiple users to organizations in bulk, such as during team migrations or organizational restructuring. The operation returns a job_status payload; the initial status is typically ‘queued’ for larger batches.Input Parameters
Output
Merge Zendesk Organizations
Merge Zendesk Organizations
ZENDESK_CREATE_ORGANIZATION_MERGEMerge two Zendesk organizations by combining all users, tickets, and data from the losing organization into the winning organization. This action is irreversible — once merged, the losing organization and all its data cannot be recovered. Use when you need to consolidate duplicate organizations or combine organization data into a single organization.Input Parameters
Output
Create Organization Subscription
Create Organization Subscription
ZENDESK_CREATE_ORGANIZATION_SUBSCRIPTIONCreate an organization subscription in Zendesk. This subscribes a user to receive notifications and updates related to a specific organization. Use when you need to add a user to an organization’s subscription list so they can access organization-related resources and receive notifications.Input Parameters
Output
Create Or Update Many Users
Create Or Update Many Users
ZENDESK_CREATE_OR_UPDATE_MANY_USERSCreate or update up to 100 Zendesk users in a single request; new users require a name. Returns a background job status, with per-user results when available.Input Parameters
Output
Create Or Update Organization
Create Or Update Organization
ZENDESK_CREATE_OR_UPDATE_ORGANIZATIONCreate or update a Zendesk organization in a single operation. If an organization with the same external_id already exists, it is updated. Otherwise, a new organization is created. Use when you need to ensure an organization exists without checking for duplicates first. Note: For updates, you must specify the external_id to match the existing organization. Name is not available as a matching criteria.Input Parameters
Output
Create or Update User
Create or Update User
ZENDESK_CREATE_OR_UPDATE_USERCreate or update a Zendesk user, matching existing users by email or external_id. Returns the user object.Input Parameters
name is mandatory. The user is matched by email or external_id to determine create vs update. role must be one of: ‘end-user’, ‘agent’, or ‘admin’.Output
Bulk Unregister Push Notification Devices
Bulk Unregister Push Notification Devices
ZENDESK_CREATE_PUSH_NOTIFICATION_DEVICES_DESTROY_MANYBulk unregister push notification devices in Zendesk. This action is irreversible — the devices will be permanently removed from receiving push notifications and cannot be recovered once removed. Use when cleaning up obsolete device tokens or removing test devices from receiving push notifications.Input Parameters
Output
Create Resource Collection
Create Resource Collection
ZENDESK_CREATE_RESOURCE_COLLECTIONSCreate a resource collection in Zendesk. Use when you need to batch multiple operations on Zendesk resources (like tickets) into a single request. The API processes the collection as a background job and returns a job status object. Note: This action queues a background job. Poll the returned job_status.url to check when the collection has been processed.Input Parameters
Output
Create Side Conversation
Create Side Conversation
ZENDESK_CREATE_SIDE_CONVERSATIONCreate a private side conversation on a Zendesk ticket. Side conversations are agent-to-agent communications that don’t notify the customer. Use this action when you need to discuss a ticket privately with another agent, escalate to a specialist, or coordinate on sensitive issues without customer visibility. Recipients can include Zendesk users (by ID or email), Slack channels, support groups, or Microsoft Teams channels.Input Parameters
Output
Create Support Address
Create Support Address
ZENDESK_CREATE_SUPPORT_ADDRESSCreate a new support address (recipient address) in Zendesk. Use when you need to add a new email address for receiving support requests. The email address must follow Zendesk’s format ({local-part}@{accountname}.zendesk.com) for internal addresses, or be an existing external email with forwarding properly configured. The created address will have verification statuses that indicate whether DNS records (CNAME, SPF) are properly configured. Note that you cannot change the email address of an existing support address after creation.Input Parameters
Output
Export Suspended Tickets
Export Suspended Tickets
ZENDESK_CREATE_SUSPENDED_TICKETS_EXPORTExport Suspended Tickets from Zendesk Support. Use when you need to export all suspended tickets for compliance review, audit purposes, or data analysis. This action enqueues a job that creates a CSV file; when complete, Zendesk emails the requester a link to download the CSV. Suspended tickets are sorted by update timestamp in ascending order. Rate limited to one request per minute. Note: This action is read-only and returns the export job status. The actual CSV will be sent via email when the job completes.Output
Create Ticket Content Pin
Create Ticket Content Pin
ZENDESK_CREATE_TICKET_CONTENT_PINCreate a ticket content pin in Zendesk. Content pins allow you to attach helpful resources like Help Center articles or external content directly to tickets for easy reference. Use this action when you need to: - Attach a Help Center article to a ticket for context - Pin an external knowledge base article to a ticket - Add relevant documentation or resources to a support ticketInput Parameters
Output
Create Ticket Field
Create Ticket Field
ZENDESK_CREATE_TICKET_FIELDCreate a custom ticket field in Zendesk with various field types. Use when you need to add a new custom field (such as text, dropdown, checkbox, date, numeric, regex-validated, or lookup) to capture additional information on tickets. The field title is required; description, required flag, and custom options are optional.Input Parameters
Output
Create Ticket Field Option
Create Ticket Field Option
ZENDESK_CREATE_TICKET_FIELD_OPTIONCreate or update an option for a dropdown or multiselect ticket field. Use when you need to add a new selectable option to a custom ticket field of type ‘multiselect’ or ‘tagger’. If an option with the same value already exists, it will be updated with the provided name. This action is idempotent - running it multiple times with the same value will update the existing option rather than creating duplicates.Input Parameters
Output
Create Trigger
Create Trigger
ZENDESK_CREATE_TRIGGERCreate a new trigger in Zendesk. Triggers are business rules that automatically perform actions on tickets when certain conditions are met. Unlike automations, triggers execute immediately when tickets are created or updated. Use this action when you need to: - Automatically change ticket status based on conditions - Assign tickets to agents or groups based on rules - Add tags to tickets matching certain criteria - Send notifications to agents, groups, or external systems - Update custom fields based on ticket properties Note: Triggers must have at least one condition in the ‘all’ array that references a time-based field (like created_at, updated_at) OR checks one of: status, type, group_id, assignee_id, requester_id, custom_status_id.Input Parameters
Output
Create Trigger Categories Batch Job
Create Trigger Categories Batch Job
Create Zendesk Trigger Category
Create Zendesk Trigger Category
ZENDESK_CREATE_TRIGGER_CATEGORYCreate a new trigger category in Zendesk. Trigger categories are used to organize and group triggers for better management. Use when setting up automated workflows or organizing business rules. This action creates a trigger category with the specified name and optional position. The name must be unique within the account.Input Parameters
Output
Create User Field Option
Create User Field Option
ZENDESK_CREATE_USER_FIELD_OPTIONCreate or update an option for a dropdown or multiselect user field. Use when you need to add a new selectable option to a custom user field of type ‘multiselect’ or ‘tagger’. If an option with the same value already exists, it will be updated with the provided name. This action is idempotent - running it multiple times with the same value will update the existing option rather than creating duplicates.Input Parameters
Output
Create User Identity
Create User Identity
ZENDESK_CREATE_USER_IDENTITYTool to add an identity to a user’s profile in Zendesk. An agent can add multiple identities to a user (e.g., multiple email addresses). Use this when a user needs to be contacted via a new channel or needs an additional identifier. Use when you need to add an additional identity (email, phone, social) to an existing Zendesk user.Input Parameters
Output
Create User Profile Event
Create User Profile Event
ZENDESK_CREATE_USER_PROFILES_EVENTSStore an event against a Sunshine user profile identified by the supplied identifiers, creating the profile if it does not exist. Event properties are limited to name and description.Input Parameters
Output
Logout Many Zendesk Users
Logout Many Zendesk Users
ZENDESK_CREATE_USERS_LOGOUT_MANYLog out multiple users in Zendesk by ending their active sessions. This action is irreversible — the affected users will be logged out and will need to re-authenticate. Use when you need to immediately terminate sessions for multiple users (e.g., after security incident, offboarding, or credential revocation). The operation accepts up to 100 user IDs at a time.Input Parameters
Output
Create User Organization Membership
Create User Organization Membership
ZENDESK_CREATE_USERS_ORGANIZATION_MEMBERSHIPSCreate a new organization membership for a specific user in Zendesk by assigning a user to an organization. Use when you need to associate an existing user with an organization so they can access organization-specific tickets and data. This action targets a specific user by their ID. This action is idempotent in that creating a duplicate membership will fail with a specific error, but the operation itself is not naturally idempotent.Input Parameters
Output
Create View
Create View
ZENDESK_CREATE_VIEWCreate a new view in Zendesk. Views are saved ticket filters that help agents organize and prioritize their work. They can filter tickets by conditions like status, priority, assignee, and more. Use this action when you need to: - Create a custom view for a specific team or workflow - Set up views for different ticket priorities or statuses - Create views with restricted access for specific groups - Configure views with specific columns, grouping, and sort order Note: At minimum, the ‘all’ conditions must include a condition checking ‘status’, ‘type’, ‘group_id’, ‘assignee_id’, or ‘requester_id’.Input Parameters
Output
Preview View
Preview View
ZENDESK_CREATE_VIEWS_PREVIEWPreview a Zendesk view by constructing conditions and execution settings to see which tickets match. Use when you need to test or validate view conditions before saving, or to retrieve a live preview of tickets matching specific filter criteria without creating a permanent view. This action is useful for verifying view logic, testing conditions, and previewing results before committing to a saved view.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
Preview View Ticket Count
Preview View Ticket Count
ZENDESK_CREATE_VIEWS_PREVIEW_COUNTPreview ticket count for a view in Zendesk. Returns the number of tickets matching the specified conditions before saving the view. Use when you want to verify how many tickets will match a view’s filter criteria before creating or updating a view. This action sends a POST request to /api/v2/views/preview/count with view conditions and returns the matching ticket count. Rate limited to 5 requests per minute, per view, per agent.Input Parameters
Output
Upload Zendesk Attachment
Upload Zendesk Attachment
ZENDESK_CREATE_ZENDESK_ATTACHMENTSUpload a file attachment to Zendesk for use in a ticket comment, returning attachment details and an upload token valid for 60 minutes. Use an uploaded file reference, data URL, or permitted local file URL.Input Parameters
Output
Create Zendesk Custom Object
Create Zendesk Custom Object
ZENDESK_CREATE_ZENDESK_CUSTOM_OBJECTCreate a new custom object in Zendesk. Use when you need to define a new custom object type to store and manage custom data. The key is immutable once created, so choose carefully.Input Parameters
Output
Create Zendesk Custom Object Field
Create Zendesk Custom Object Field
ZENDESK_CREATE_ZENDESK_CUSTOM_OBJECT_FIELDCreate a new field for a custom object in Zendesk. Use when you need to add a new attribute or data field to an existing custom object type. The key is immutable once created. This action is idempotent for the same key, but the key parameter must be unique per custom object.Input Parameters
Output
Create Zendesk Group
Create Zendesk Group
ZENDESK_CREATE_ZENDESK_GROUPCreate a Zendesk group with an account-unique name to organize agents for ticket assignment and routing. Returns the group’s assigned ID and supported group fields.Input Parameters
Output
Import Zendesk Ticket
Import Zendesk Ticket
ZENDESK_CREATE_ZENDESK_IMPORT_TICKETImport a ticket into Zendesk with historical timestamps. This action creates tickets with past created_at, updated_at, or solved_at values, useful for migrating historical data. For real-time ticket creation, use ZENDESK_CREATE_ZENDESK_TICKET. Tickets created with ‘closed’ status and archive_immediately=true bypass normal lifecycle and go directly to archive.Input Parameters
Output
Create Zendesk Organization
Create Zendesk Organization
ZENDESK_CREATE_ZENDESK_ORGANIZATIONCreate a new organization in Zendesk. After creation, the organization ID is auto-assigned and returned. Verify the exact ID before performing downstream operations that target this organization. Multiple organizations may share similar names — always confirm the correct organization by ID. This action is irreversible — the organization cannot be recovered once deleted. Use this action when you need to register a new company, customer, or group as a Zendesk organization so you can assign users, tickets, or other resources to it.Input Parameters
Output
Create Zendesk Request
Create Zendesk Request
ZENDESK_CREATE_ZENDESK_REQUESTCreate a new request in Zendesk. Use when an end user needs to submit a support request through the API. The request will be created with the provided subject, description, priority, and other optional fields. Returns the created request with its ID and URL.Input Parameters
comment as mandatory (confirmed live: omitting it returns a 422).Output
Create Zendesk Target
Create Zendesk Target
ZENDESK_CREATE_ZENDESK_TARGETCreate a target in Zendesk for triggering outbound integrations. Use when you need to set up a notification channel or integration with external services like Campfire, email, URL webhooks, or other supported targets. Targets can be used with triggers and automation rules. Note: URL targets are being discontinued October 28, 2024 in favor of webhooks. Email targets remain unaffected.Input Parameters
Output
Create Zendesk Ticket
Create Zendesk Ticket
ZENDESK_CREATE_ZENDESK_TICKETCreate a Zendesk ticket with a subject and initial comment, plus optional ticket properties such as priority, status, assignment, tags, collaborators, followers and custom fields. Returns the ticket ID, agent URL and selected ticket properties.Input Parameters
requester_email. Leave both blank to default to the authenticated user. Ignored if requester_id is provided.Output
Create Ticket or Voicemail Ticket
Create Ticket or Voicemail Ticket
ZENDESK_CREATE_ZENDESK_TICKET_OR_VOICEMAIL_TICKETCreate a ticket in Zendesk via the voice/channel API endpoint. Use this action when you need to create tickets from phone calls, voicemails, or other voice channel interactions. Returns ticket_id and ticket_url for the created ticket. This endpoint is specifically for Zendesk Talk/voice channel ticket creation.Input Parameters
requester_email. Leave both blank to default to the authenticated user. Ignored if requester_id is provided.Output
Create Zendesk User
Create Zendesk User
ZENDESK_CREATE_ZENDESK_USERTool to create a new user in Zendesk. Search for existing users first to avoid duplicate accounts with the same email. Use when you need to onboard a user with specific details.Input Parameters
name is mandatory; omitting it causes a validation error. role must be one of: ‘end-user’, ‘agent’, or ‘admin’. organization_id must be a numeric ID of an existing organization — not a name string. Only include fields supported by the Zendesk user schema; unsupported or incorrectly typed fields trigger validation errors.Output
Create Zendesk User Field
Create Zendesk User Field
ZENDESK_CREATE_ZENDESK_USER_FIELDCreate a custom user field in Zendesk. Use when you need to define a new custom field to capture additional user data. Supports text, checkbox, dropdown, multiselect, date, integer, decimal, regexp validation, and lookup types. Only administrators can create user fields.Input Parameters
Output
Delete Access Rule
Delete Access Rule
Delete Zendesk Automation
Delete Zendesk Automation
ZENDESK_DELETE_AUTOMATIONPermanently deletes an automation in Zendesk. This action is irreversible — the automation will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete automations or removing test data. Note: You might be restricted from deleting automations that are active or referenced by other rules.Input Parameters
Output
Delete Zendesk Business Hours Schedule
Delete Zendesk Business Hours Schedule
ZENDESK_DELETE_BUSINESS_HOURS_SCHEDULEPermanently deletes a business hours schedule in Zendesk. Use when you need to remove obsolete schedules or clean up test data. This action is irreversible — the schedule cannot be recovered once removed. Admin permissions are required. Note: Schedules that are currently in use by active SLA policies or other configurations may not be deletable.Input Parameters
Output
Delete Custom Object Record Attachment
Delete Custom Object Record Attachment
ZENDESK_DELETE_CUSTOM_OBJECT_RECORD_ATTACHMENTPermanently deletes an attachment from a custom object record in Zendesk. Use this action when you need to remove a specific file attachment from a custom object record. This action is irreversible — the attachment will be permanently deleted and cannot be recovered once removed. Note: Only attachments that are not required and not the primary attachment can be deleted.Input Parameters
Output
Delete Custom Object Record
Delete Custom Object Record
ZENDESK_DELETE_CUSTOM_OBJECT_RECORD_BY_EXTERNAL_ID_OR_NAMEPermanently deletes a custom object record in Zendesk by its external ID or name. Use this action when you need to remove a specific record from a custom object. This action is irreversible — the record cannot be recovered once deleted. Requires admin permissions. Note: Either external_id or name must be provided to identify the record to delete.Input Parameters
Output
Delete Deleted Ticket Permanently
Delete Deleted Ticket Permanently
Delete Zendesk Deletion Schedule
Delete Zendesk Deletion Schedule
ZENDESK_DELETE_DELETION_SCHEDULEPermanently deletes a deletion schedule in Zendesk. This action is irreversible — the deletion schedule will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete deletion schedules or removing test data.Input Parameters
Output
Delete Zendesk Group Membership
Delete Zendesk Group Membership
ZENDESK_DELETE_GROUP_MEMBERSHIPPermanently deletes a group membership in Zendesk, immediately removing a user from a group. This action is irreversible — the group membership cannot be recovered once deleted. Use when cleaning up obsolete group memberships or removing users from groups. Note: Deleting a group membership does not delete the user or the group itself, only the association between them.Input Parameters
Output
Bulk Delete Zendesk Group Memberships
Bulk Delete Zendesk Group Memberships
ZENDESK_DELETE_GROUP_MEMBERSHIPS_DESTROY_MANYBulk delete Zendesk group memberships by ID. Returns a job status for tracking the asynchronous deletion of the memberships.Input Parameters
Output
Delete Zendesk Macro
Delete Zendesk Macro
ZENDESK_DELETE_MACROPermanently deletes a macro in Zendesk. This action is irreversible — the macro will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete macros or removing test data. Note: You might be restricted from deleting macros that are active or referenced by other rules.Input Parameters
Output
Bulk Delete Zendesk Macros
Bulk Delete Zendesk Macros
Bulk Delete Zendesk Automations
Bulk Delete Zendesk Automations
Bulk Delete Zendesk Custom Object Triggers
Bulk Delete Zendesk Custom Object Triggers
ZENDESK_DELETE_MANY_OBJECT_TRIGGERSBulk delete triggers for a Zendesk custom object. This action is irreversible — the triggers will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete triggers or removing test data for a specific custom object. Returns a success indicator upon completion. Requires the custom object key and a comma-separated list of trigger IDs to identify which triggers to delete.Input Parameters
Output
Bulk Delete Zendesk Organization Memberships
Bulk Delete Zendesk Organization Memberships
ZENDESK_DELETE_MANY_ORGANIZATION_MEMBERSHIPSBulk delete organization memberships in Zendesk. This action is irreversible — the memberships will be permanently removed and cannot be recovered once deleted. Use when cleaning up obsolete organization memberships or removing users from organizations. Returns a job_status payload (initial status typically ‘queued’); deletions complete asynchronously and may require follow-up polling to confirm completion.Input Parameters
Output
Bulk Delete Zendesk Views
Bulk Delete Zendesk Views
Delete Zendesk Organization Field
Delete Zendesk Organization Field
ZENDESK_DELETE_ORGANIZATION_FIELDPermanently deletes an organization field in Zendesk. Use this action when you need to remove a custom organization field from the system. This action is irreversible — the organization field will be permanently deleted and cannot be recovered once removed. Any data stored in this field across all organizations will be lost. Note: Ensure no organizations are using this field before deletion, as the deletion cannot be undone.Input Parameters
Output
Delete Organization Membership
Delete Organization Membership
ZENDESK_DELETE_ORGANIZATION_MEMBERSHIPPermanently removes a user from an organization in Zendesk by deleting the organization membership. This action is irreversible — the membership cannot be recovered once deleted. Use this action when you need to remove a user’s association with an organization. This operation requires admin permissions.Input Parameters
Output
Delete Zendesk Organization Subscription
Delete Zendesk Organization Subscription
Delete Resource Collection
Delete Resource Collection
ZENDESK_DELETE_RESOURCE_COLLECTIONSDelete a resource collection in Zendesk. Use when you need to remove a resource collection that is no longer needed. This action returns a job status that can be polled to track the deletion progress. This operation is irreversible; confirm the correct resource_collection_id before executing.Input Parameters
Output
Bulk Delete Zendesk Suspended Tickets
Bulk Delete Zendesk Suspended Tickets
ZENDESK_DELETE_SUSPENDED_TICKETS_DESTROY_MANYPermanently deletes multiple suspended tickets in Zendesk. This action is irreversible — the suspended tickets will be permanently deleted and cannot be recovered once removed. Use when cleaning up spam or irrelevant suspended tickets. Accepts up to 100 ticket IDs per request.Input Parameters
Output
Delete Zendesk Target
Delete Zendesk Target
ZENDESK_DELETE_TARGETPermanently deletes a target in Zendesk. This action is irreversible — the target will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete targets or removing test data. Note: Deleting a target that is actively used by triggers or other automation rules may cause those rules to fail.Input Parameters
Output
Delete Zendesk Ticket Field
Delete Zendesk Ticket Field
ZENDESK_DELETE_TICKET_FIELDPermanently deletes a ticket field in Zendesk. Use this action when you need to remove a custom ticket field that is no longer needed. This action is irreversible — the ticket field and all associated data will be permanently deleted and cannot be recovered once removed. Requires admin permissions. Note: System ticket fields cannot be deleted. Only custom ticket fields can be removed.Input Parameters
creator_user_id and creator_app_name properties in the response. If the ticket field is created by an app, creator_app_name is the name of the app and creator_user_id is -1. If the ticket field is not created by an app, then creator_app_name is nullOutput
Delete Ticket Field Option
Delete Ticket Field Option
ZENDESK_DELETE_TICKET_FIELD_OPTIONPermanently deletes an option from a ticket field in Zendesk. Use this action when you need to remove a specific selectable option from a dropdown or multiselect ticket field. This action is irreversible — the ticket field option will be permanently deleted and cannot be recovered once removed. Note: Only custom options can be deleted. System-defined options cannot be removed.Input Parameters
Output
Delete Zendesk Trigger
Delete Zendesk Trigger
ZENDESK_DELETE_TRIGGERPermanently deletes a trigger in Zendesk. This action is irreversible — the trigger will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete triggers or removing test data. Note: You might be restricted from deleting triggers that are active or referenced by other rules.Input Parameters
Output
Delete Zendesk Trigger Category
Delete Zendesk Trigger Category
ZENDESK_DELETE_TRIGGER_CATEGORYPermanently deletes a trigger category in Zendesk. This action is irreversible — the trigger category will be permanently deleted and cannot be recovered once removed. Use when cleaning up obsolete trigger categories or removing test data. Note: You might be restricted from deleting trigger categories that are in use by active triggers.Input Parameters
Output
Delete Zendesk User Field
Delete Zendesk User Field
Delete User Field Option
Delete User Field Option
ZENDESK_DELETE_USER_FIELD_OPTIONPermanently deletes an option from a user field in Zendesk. Use this action when you need to remove a specific selectable option from a dropdown or multiselect user field. This action is irreversible — the user field option will be permanently deleted and cannot be recovered once removed.Input Parameters
Output
Permanently Delete User
Permanently Delete User
ZENDESK_DELETE_USER_PERMANENTLYPermanently deletes a soft-deleted user from Zendesk. This action is irreversible - once a user is permanently deleted, it cannot be recovered. Use this action to remove users that were previously soft-deleted using the delete_user action. Use this action when you need to permanently remove a user that has already been deleted and is no longer accessible through normal operations. This action requires appropriate admin permissions.Input Parameters
Output
Delete Zendesk User Profile
Delete Zendesk User Profile
ZENDESK_DELETE_USER_PROFILEPermanently deletes a user profile in Zendesk by its profile ID. This action is irreversible — the profile and all associated data will be permanently lost. Use when cleaning up duplicate profiles, test profiles, or removing profiles that are no longer needed. Requires agent-level access with appropriate role permissions.Input Parameters
Output
Bulk Delete Zendesk Users
Bulk Delete Zendesk Users
ZENDESK_DELETE_USERS_DESTROY_MANYBulk delete users from Zendesk by their IDs or external IDs. This action is irreversible — once deleted, users cannot be recovered. Use when cleaning up test data, removing obsolete accounts, or consolidating user records in bulk. The operation returns a job_status payload (initial status typically ‘queued’); deletions complete asynchronously and may require follow-up polling via the job_status URL to confirm completion.Input Parameters
Output
Delete Zendesk User Session
Delete Zendesk User Session
ZENDESK_DELETE_USER_SESSIONDelete a specific user session in Zendesk. Use this action when you need to invalidate and remove a specific user session. This action is irreversible — the session cannot be recovered once deleted. Use when you need to forcibly log out a user or remove a specific session from their account for security or administrative purposes.Input Parameters
Output
Delete Zendesk User's Group Membership
Delete Zendesk User's Group Membership
ZENDESK_DELETE_USERS_GROUP_MEMBERSHIPSPermanently deletes a user’s group membership in Zendesk, immediately removing a user from a group. This action is irreversible — the group membership cannot be recovered once deleted. Use when cleaning up obsolete group memberships, removing users from groups, or revoking group access. Note: Deleting a group membership does not delete the user or the group itself, only the association between them. The user will no longer have access to tickets routed to that group.Input Parameters
Output
Delete User Identity
Delete User Identity
ZENDESK_DELETE_USERS_IDENTITYDeletes an identity for a given user in Zendesk. Use when you need to remove a specific identity (e.g., email, phone, social login) from a user’s account. This action is irreversible — once the identity is deleted, it cannot be recovered. Ensure you have the correct user_id and user_identity_id before executing.Input Parameters
Output
Delete Authenticated Session
Delete Authenticated Session
ZENDESK_DELETE_USERS_ME_LOGOUTDelete the current authenticated session in Zendesk. This action invalidates the current API session, requiring re-authentication for future API calls. Use when you need to explicitly log out the current user session or terminate an active authenticated connection. This action is irreversible — the session cannot be recovered once deleted. Note: This action targets the authenticated user’s own session only and cannot terminate other user sessions.Output
Delete User's Organization Membership
Delete User's Organization Membership
ZENDESK_DELETE_USERS_ORGANIZATION_MEMBERSHIPSPermanently removes a user from an organization in Zendesk by deleting the organization membership for a specific user. This action is irreversible — the membership cannot be recovered once deleted. Use this action when you need to remove a user’s association with an organization for a specific user. This operation requires admin permissions.Input Parameters
Output
Delete All User Sessions
Delete All User Sessions
ZENDESK_DELETE_USERS_SESSIONSBulk delete all sessions for a specific user in Zendesk. This action invalidates all active sessions for the specified user, forcing them to re-authenticate on their next API call or login. Use when you need to forcibly log out a user by revoking all their active sessions, such as during security incidents or account deactivation. This action is irreversible — all sessions for the user will be immediately invalidated and cannot be recovered.Input Parameters
Output
Delete Zendesk View
Delete Zendesk View
Delete Zendesk App Installation
Delete Zendesk App Installation
ZENDESK_DELETE_ZENDESK_APP_INSTALLATIONPermanently removes an installed app from Zendesk. Use when you need to uninstall an app from your Zendesk instance. This action is irreversible — the app installation cannot be recovered once removed. Admin permissions are required.Input Parameters
Output
Delete Zendesk Bookmark
Delete Zendesk Bookmark
Delete Zendesk Custom Object
Delete Zendesk Custom Object
ZENDESK_DELETE_ZENDESK_CUSTOM_OBJECTPermanently deletes a custom object definition in Zendesk. Use this action when you need to remove a custom object type and all its associated records. This action is irreversible — the custom object and all its data will be permanently deleted and cannot be recovered once removed. Requires admin permissions. Note: Deleting a custom object will also delete all records associated with it.Input Parameters
Output
Delete Zendesk Custom Object Field
Delete Zendesk Custom Object Field
ZENDESK_DELETE_ZENDESK_CUSTOM_OBJECT_FIELDPermanently deletes a custom object field in Zendesk. Use this action when you need to remove a specific field from a custom object definition. This action is irreversible — the field and all its data will be permanently deleted and cannot be recovered once removed. Requires admin permissions.Input Parameters
Output
Delete Zendesk Custom Object Record
Delete Zendesk Custom Object Record
Delete Zendesk Custom Status
Delete Zendesk Custom Status
ZENDESK_DELETE_ZENDESK_CUSTOM_STATUSPermanently deletes a custom ticket status in Zendesk. Use this action when you need to remove a custom ticket status from the system. This action is irreversible — the custom status will be permanently deleted and cannot be recovered once removed. Note: Ensure no tickets are using this custom status before deletion.Input Parameters
Output
Delete Zendesk Dynamic Content Item
Delete Zendesk Dynamic Content Item
Delete Zendesk Dynamic Content Item Variant
Delete Zendesk Dynamic Content Item Variant
ZENDESK_DELETE_ZENDESK_DYNAMIC_CONTENT_ITEM_VARIANTPermanently deletes a dynamic content item variant in Zendesk. This action is irreversible — the variant cannot be recovered once deleted. Always confirm the correct dynamic_content_item_id and dynamic_content_variant_id before executing.Input Parameters
Output
Delete Zendesk Custom Object Trigger
Delete Zendesk Custom Object Trigger
ZENDESK_DELETE_ZENDESK_OBJECT_TRIGGERPermanently deletes a custom object trigger in Zendesk. Use this action when you need to remove a specific trigger from a custom object definition. This action is irreversible — the trigger and all its data will be permanently deleted and cannot be recovered once removed. Requires admin permissions.Input Parameters
Output
Delete Zendesk Organization
Delete Zendesk Organization
Delete Zendesk Support Address
Delete Zendesk Support Address
ZENDESK_DELETE_ZENDESK_SUPPORT_ADDRESSPermanently deletes a support address from Zendesk. This action is irreversible — the support address cannot be recovered once deleted. Use this action when you need to remove a deprecated or unwanted support email address from your Zendesk account. This operation requires admin permissions and the support address must not be set as the default address. Deleting an address that is actively used may impact email routing.Input Parameters
Output
Delete Zendesk Ticket
Delete Zendesk Ticket
Delete Zendesk User
Delete Zendesk User
Bulk Delete Soft-Deleted Zendesk Tickets
Bulk Delete Soft-Deleted Zendesk Tickets
ZENDESK_DESTROY_MANY_DELETED_TICKETSPermanently deletes multiple soft-deleted tickets in Zendesk. This action is irreversible — the tickets will be permanently removed and cannot be recovered once executed. Use when cleaning up test tickets or removing obsolete soft-deleted tickets in bulk. The operation returns a job_status payload (initial status typically ‘queued’); deletions complete asynchronously and may require follow-up polling to confirm completion. Maximum 100 tickets per request.Input Parameters
Output
Bulk Delete Zendesk Organizations
Bulk Delete Zendesk Organizations
ZENDESK_DESTROY_MANY_ORGANIZATIONSBulk delete Zendesk organizations. This action is irreversible - once organizations are deleted, they cannot be recovered. Use when you need to remove multiple organizations in a single operation. Returns a job_status payload (initial status typically ‘queued’); deletions complete asynchronously and may require follow-up polling to confirm completion. Maximum 100 organizations per request. Use this action when you need to clean up test data, remove obsolete organizations, or perform bulk organization deletions. You must provide either ‘ids’ (comma-separated list of Zendesk organization IDs) or ‘external_ids’ (comma-separated list of external IDs).Input Parameters
Output
Detect Best Locale
Detect Best Locale
Download Attachment
Download Attachment
Download Custom Object Record Attachment
Download Custom Object Record Attachment
ZENDESK_DOWNLOAD_CUSTOM_OBJECT_RECORD_ATTACHMENTDownload an attachment from a Zendesk custom object record and return it as a downloadable file. An inline option is sent to Zendesk with the request.Input Parameters
Output
Get Zendesk About Me
Get Zendesk About Me
ZENDESK_GET_ABOUT_MEGet information about the currently authenticated user in Zendesk. Returns only the caller’s own account; to look up other users, use ZENDESK_SEARCH_ZENDESK_USERS. Response nests the user object under data.owner_info.user. Useful for verifying the acting user’s identity and permissions before performing bulk operations.Output
Get Account Settings
Get Account Settings
List Active Triggers
List Active Triggers
ZENDESK_GET_ACTIVE_TRIGGERSList a page of active Zendesk ticket triggers, including their conditions, actions, and metadata when returned. Supports pagination, sorting, and category filtering for auditing automation rules.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). Mutually exclusive.Output
Count Activities
Count Activities
Get Zendesk Organizations
Get Zendesk Organizations
Get App
Get App
Get App Installation Requirements
Get App Installation Requirements
ZENDESK_GET_APPS_INSTALLATIONS_REQUIREMENTSList all requirements for a Zendesk app installation. Use when you need to check what configuration or parameters are required for a specific installed app to function properly. Requirements may include OAuth settings, parameter configurations, or other setup steps needed by the app. This action is read-only and idempotent.Input Parameters
Output
Get App Location
Get App Location
ZENDESK_GET_APPS_LOCATIONGet details for a specific Zendesk app location by its numeric ID. Returns location properties including visibility settings, orderability, and associated product codes. Use when you have an app_location_id from listing locations or creating apps and need to retrieve detailed location information. Only accessible to admin users.Input Parameters
Output
List Apps Location Installations
List Apps Location Installations
Get App Public Key
Get App Public Key
ZENDESK_GET_APPS_PUBLIC_KEYRetrieves the public key for a specific Zendesk app. The response is in JSON Web Key (JWK) format containing RSA key components (modulus n, exponent e). Use this action when you need to verify JWTs issued by a Zendesk app or establish trust for app-based authentication. This is a read-only operation.Input Parameters
Output
Get App Public Key PEM
Get App Public Key PEM
ZENDESK_GET_APPS_PUBLIC_KEY_PEMRetrieve a specific Zendesk app’s public key in PEM format. This read-only action can be used to verify app-issued JWTs or establish trust for app-based authentication.Input Parameters
Output
Get Attachment
Get Attachment
Show Automation
Show Automation
ZENDESK_GET_AUTOMATIONShow a specific automation by its ID. Use when you need to retrieve details of a single automation rule in your Zendesk account, such as for auditing, modifying, or understanding what actions and conditions are configured for a particular automation. This action is read-only and idempotent.Input Parameters
Output
List Automations
List Automations
ZENDESK_GET_AUTOMATIONSList Zendesk automations for review or auditing, with page and page-size parameters and an optional active-status filter.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering. Example: ?sort=name or ?sort=-created_atOutput
Search Automations
Search Automations
ZENDESK_GET_AUTOMATIONS_SEARCHSearch for Zendesk automations by their title. Use when you need to find automations in your Zendesk account by searching for keywords in their titles. Automations are business rules that automatically perform actions when certain conditions are met. This action supports filtering by active status and sorting results.Input Parameters
Output
List Brands
List Brands
ZENDESK_GET_BRANDSList Zendesk brands and retrieve metadata such as default status, subdomain, and host mapping. Supports cursor pagination and a per-page parameter.Input Parameters
- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
Get Zendesk Brand
Get Zendesk Brand
ZENDESK_GET_BRANDS2Show a Brand. Use when you have a brand ID and need to retrieve detailed information about a specific Zendesk brand, including its name, subdomain, active status, Help Center configuration, logo, and associated ticket forms.Input Parameters
Output
List Agents by Brand
List Agents by Brand
ZENDESK_GET_BRANDS_AGENTSList agents assigned to a specific brand in Zendesk. Use when you need to enumerate which agents have access to a specific brand, such as auditing brand access permissions or determining which agents can access a brand’s help center. This is a read-only, idempotent operation.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
Get Custom Object Fields Limit
Get Custom Object Fields Limit
ZENDESK_GET_CUSTOM_OBJECT_FIELDS_LIMITGet the current count and maximum limit for custom object fields in Zendesk. Returns the number of fields currently defined for a specific custom object and the maximum allowed limit. Use when you need to check how many fields have been created for a custom object and how much capacity remains before hitting the limit. This is a read-only operation that does not modify any data.Input Parameters
Output
Get Custom Object Records Limit
Get Custom Object Records Limit
ZENDESK_GET_CUSTOM_OBJECT_RECORDS_LIMITGet the current record limit and usage count for custom objects in Zendesk. Returns the current number of custom object records and the maximum allowed limit. Use when you need to check how many custom object records have been created and how much capacity remains. This is a read-only operation that does not modify any data.Output
Get Custom Objects Limit
Get Custom Objects Limit
Get Custom Status
Get Custom Status
ZENDESK_GET_CUSTOM_STATUSGet a specific custom ticket status from Zendesk by its ID. Use when you have a custom status ID from ticket payloads or from listing custom statuses and need to retrieve the full status details including agent/end-user labels, descriptions, and status category. This is a read-only, idempotent operation that retrieves the current state of a custom ticket status.Input Parameters
Output
List Custom Ticket Statuses
List Custom Ticket Statuses
ZENDESK_GET_CUSTOM_STATUSESList custom ticket statuses available in a Zendesk account. Use when you need to retrieve all undeleted custom ticket statuses, optionally filtered by status category, active state, or default status. This action is useful for understanding available custom statuses for ticket workflows, automation rules, or displaying status options to users.Input Parameters
Output
List Deleted Tickets
List Deleted Tickets
ZENDESK_GET_DELETED_TICKETSLists tickets that have been deleted from Zendesk, showing up to 100 deleted tickets per page with pagination. Use when you need to retrieve information about previously deleted tickets or audit ticket deletions. This action is read-only and idempotent.Input Parameters
Output
Get Deleted User
Get Deleted User
ZENDESK_GET_DELETED_USERRetrieves a single deleted Zendesk user by their ID. Use when you have a specific deleted user ID and need to fetch details about that deleted user, such as for auditing purposes, account recovery, or compliance records. Deleted users retain their associated tickets and historical data.Input Parameters
Output
Get Deletion Schedule
Get Deletion Schedule
ZENDESK_GET_DELETION_SCHEDULERetrieve a specific deletion schedule from Zendesk by its ID. Use this action when you need to get the details of a particular deletion schedule, including its title, description, active status, object type, conditions, and creation/update timestamps. This action is read-only and idempotent.Input Parameters
Output
List Deletion Schedules
List Deletion Schedules
ZENDESK_GET_DELETION_SCHEDULESList all deletion schedules for the current Zendesk account. Use when you need to retrieve, audit, or review the deletion schedule rules configured in your Zendesk account. Deletion schedules define automated data retention policies that periodically remove specified entity types based on configured conditions. Only Zendesk admins can access this endpoint.Output
List Dynamic Content Items
List Dynamic Content Items
ZENDESK_GET_DYNAMIC_CONTENT_ITEMSList dynamic content items configured in your Zendesk account, including localization variants and placeholder metadata. This read-only operation supports offset pagination and sorting.Input Parameters
?page=2 (integer page number), or cursor using ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive.- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
Show Dynamic Content Item
Show Dynamic Content Item
ZENDESK_GET_DYNAMIC_CONTENT_ITEM_SHOWShow a specific dynamic content item by its ID. Use when you have a dynamic content item ID and need to retrieve its details, including name, default locale, placeholder value, variants, and creation/update timestamps. This is a read-only, idempotent operation that returns a single dynamic content item.Input Parameters
Output
Show Many Dynamic Content Items
Show Many Dynamic Content Items
ZENDESK_GET_DYNAMIC_CONTENT_ITEMS_SHOW_MANYRetrieve multiple dynamic content items by their identifiers. Use when you have specific dynamic content item IDs or names and need to fetch their metadata including placeholder, default locale, variants, and outdated status. This is a read-only, idempotent operation. The ‘identifiers’ parameter accepts comma-separated values; omit it to retrieve all items (use with caution on accounts with many items).Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). Mutually exclusive.Output
List Dynamic Content Variants
List Dynamic Content Variants
ZENDESK_GET_DYNAMIC_CONTENT_ITEMS_VARIANTSList all variants of a specific Zendesk dynamic content item. Use when you need to retrieve all locale variants for a dynamic content item to view, manage, or update the localized content. Variants represent the same content in different locales/languages. Supports pagination and sorting parameters. This action is read-only and idempotent — calling it multiple times with the same parameters will return the same results without side effects.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering. Example: ?sort=name or ?sort=-created_atOutput
Show Dynamic Content Item Variant
Show Dynamic Content Item Variant
ZENDESK_GET_DYNAMIC_CONTENT_ITEM_VARIANTShow a specific variant of a dynamic content item in Zendesk. Use when you have a dynamic_content_item_id and dynamic_content_variant_id and need to retrieve the variant’s details including its content, locale, active status, and timestamps. This is a read-only operation. Dynamic content items allow you to create reusable content that can be localized into multiple variants for different languages or contexts.Input Parameters
Output
Get Email Notification
Get Email Notification
ZENDESK_GET_EMAIL_NOTIFICATIONRetrieve details of a single email notification in Zendesk by its notification ID. Use when you have a notification_id from ticket audit logs or email notifications list and need to fetch full notification details including recipients, delivery status, and associated ticket/comment information. This action is useful for tracking email delivery status and troubleshooting email notification issues.Input Parameters
Output
Get Email Notifications
Get Email Notifications
ZENDESK_GET_EMAIL_NOTIFICATIONSList email notifications from Zendesk. Use this action when you need to retrieve email notification records filtered by ticket, comment, or notification ID. The filter parameter is required to specify which type of ID to filter by. Returns delivery status information for each recipient including any delivery failures.Input Parameters
Output
Show Many Email Notifications
Show Many Email Notifications
ZENDESK_GET_EMAIL_NOTIFICATIONS_SHOW_MANYRequest Zendesk email notifications by notification IDs, comment IDs, or ticket IDs. The response model exposes only a single optional email notification object.Input Parameters
Output
List End User Identities
List End User Identities
ZENDESK_GET_END_USER_IDENTITIESTool to list all identities associated with a specific end user. Use when you need to retrieve the email addresses and/or phone numbers linked to an end user account. Supports optional filtering by identity type (email, phone_number).Input Parameters
Output
Get End User Identity
Get End User Identity
Get Group Membership
Get Group Membership
ZENDESK_GET_GROUP_MEMBERSHIPGet a group membership by its unique ID. Use when you have a group membership ID and need to retrieve details including the associated group, user, and timestamps. Note: The group_membership_id parameter is the membership ID, not a group ID.Input Parameters
Output
List Group Memberships
List Group Memberships
ZENDESK_GET_GROUP_MEMBERSHIPSList all group memberships in your Zendesk account. Group memberships link users to groups, determining which agents belong to which support groups. Use when you need to audit group assignments, manage team memberships, or enumerate the relationship between users and groups. This action supports both offset pagination (page, per_page) and cursor pagination (page_size, page_after, page_before). It also supports sideloading related users and groups via the include parameter. This action is read-only and idempotent.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor. These are mutually exclusive.- for descending order. Example: ?sort=name or ?sort=-created_atusers, groups.Output
List Memberships By Group
List Memberships By Group
ZENDESK_GET_GROUP_MEMBERSHIPS_BY_GROUPList group memberships for a specific Zendesk group. Use when you need to retrieve all members assigned to a particular group, audit group membership, or understand which users belong to a specific support group. This action is read-only and idempotent. Supports both offset pagination (page, per_page) and cursor pagination (page_size, page_after, page_before). Also supports sideloading users and groups via the include parameter.Input Parameters
- for descending order. Example: ?sort=user_id or ?sort=-created_atusers, groups.Output
List Assignable Groups
List Assignable Groups
ZENDESK_GET_GROUPS_ASSIGNABLEList all groups that can be assigned to tickets or users in your Zendesk account. Use when you need to enumerate available groups for assignment operations, check group availability, or retrieve group metadata. This is a read-only, idempotent operation.Input Parameters
Output
Count Groups
Count Groups
Count Users by Group
Count Users by Group
ZENDESK_GET_GROUPS_USERS_COUNTCount users in a specific Zendesk group. Returns an approximate count of users belonging to the specified group, with optional filtering by role or permission set. Use when you need to know how many users are in a particular group for reporting, resource planning, or administrative purposes. This action is read-only and idempotent.Input Parameters
Output
List Group Users
List Group Users
ZENDESK_GET_GROUP_USERSList a page of users belonging to a specific Zendesk group, with optional filtering by user role, permission set, or external ID. This is a read-only operation.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive.Output
List Guide Survey Responses
List Guide Survey Responses
ZENDESK_GET_GUIDE_SURVEY_RESPONSESList survey responses from Zendesk Guide. Use when you need to retrieve CSAT survey responses, analyze customer satisfaction scores, or monitor survey completion rates. Survey responses are available on Support Professional plan and above, and Zendesk Suite Growth plan and above. This action is read-only and idempotent.Input Parameters
Output
List Guide Surveys
List Guide Surveys
ZENDESK_GET_GUIDE_SURVEYSList available CSAT (Customer Satisfaction) surveys in Zendesk Guide. Use when you need to retrieve survey definitions, check which surveys are enabled/disabled, or get survey questions and versions. The response includes survey IDs, states, creation timestamps, and question arrays. This is a read-only, idempotent operation.Input Parameters
Output
Get Incremental Organizations
Get Incremental Organizations
ZENDESK_GET_INCREMENTAL_ORGANIZATIONSRetrieve organizations that have been modified since a specified start time using the Incremental Organization Export API. Use when you need to sync or track changes to Zendesk organizations over time. Provide a start_time (Unix timestamp) from a previous response’s end_time to paginate through changes incrementally. This action is read-only and idempotent. Organizations may be created, updated, or appear as deleted; interpret based on your use case. Rate limiting may apply for large accounts.Input Parameters
Output
Incremental Routing Attributes Export
Incremental Routing Attributes Export
ZENDESK_GET_INCREMENTAL_ROUTING_ATTRIBUTESExport routing attributes incrementally with optional start_time filtering and cursor-based pagination. Use when you need to retrieve all skill-based routing attributes (attributes, attribute values, and instance values) that have changed in your Zendesk account. This is a read-only operation that returns a stream of changes; it does not include data from the most recent minute. For large datasets, use cursor-based pagination with the after_cursor value from responses. This action is read-only and idempotent — calling it multiple times with the same start_time returns the same results.Input Parameters
Output
Get Incremental Routing Attribute Values
Get Incremental Routing Attribute Values
ZENDESK_GET_INCREMENTAL_ROUTING_ATTRIBUTE_VALUESRetrieve routing attribute values that have been modified since a specified start time using the Incremental Skill-Based Routing API. Use when you need to sync or track changes to routing attributes, values, and their associations over time. Provide a start_time (Unix timestamp) and the API returns all attribute values modified since that time. Call repeatedly with the end_time from each response to paginate through all changes. This action is read-only and idempotent. Note: Data isn’t available for the most recent minute due to eventual consistency. Attribute values may appear as modified; interpret based on your use case.Input Parameters
Output
Export Incremental Routing Instance Values
Export Incremental Routing Instance Values
ZENDESK_GET_INCREMENTAL_ROUTING_INSTANCE_VALUESExport incremental routing instance values from Zendesk skill-based routing. Returns a stream of changes that occurred on routing attributes, attribute values, and instance values. Use this action when you need to synchronize routing configuration data or monitor changes to skill-based routing assignments. This action is read-only and supports cursor-based pagination with a maximum of 3000 records per page. Stop paging when the count is 0. Note: The cursor parameter is read-only and should only be obtained from API responses, not manually constructed.Input Parameters
Output
Get Incremental Sample Export
Get Incremental Sample Export
ZENDESK_GET_INCREMENTAL_SAMPLERequest a sample incremental export for a resource since a specified start time, to test an export setup. The response exposes ticket records but not user or organization record arrays; data from the most recent minute is not provided.Input Parameters
Output
Get Incremental Ticket Events
Get Incremental Ticket Events
ZENDESK_GET_INCREMENTAL_TICKET_EVENTSExport incremental ticket events from Zendesk. Use when you need to track changes to tickets over time, monitor agent performance metrics, or sync ticket event data with an external system. This action returns a stream of ticket metric events (like agent work time, reply times) that occurred after the specified start_time. Call repeatedly with the end_time from each response to continue exporting events. Data isn’t available for the most recent minute due to eventual consistency. Note: This is a read-only, idempotent operation. The start_time must be at least one minute in the past.Input Parameters
Output
List Ticket Metric Events
List Ticket Metric Events
ZENDESK_GET_INCREMENTAL_TICKET_METRIC_EVENTSList ticket metric events in Zendesk that occurred on or after a specified time. This action supports incremental data export — use the end_time from one response as the start_time for the next request to retrieve subsequent events. This action is read-only and idempotent — use it to monitor ticket metrics, track SLA compliance, or build analytics dashboards. Note: deleted tickets can create orphan metric events; use exclude_deleted=true to filter these out.Input Parameters
Output
Get Incremental Tickets
Get Incremental Tickets
ZENDESK_GET_INCREMENTAL_TICKETSRetrieve tickets modified since a specified start time using the incremental ticket export, and use the response’s end_time for subsequent requests. The support type defaults to agent; select all to include other support types, and note that data from the most recent minute is not provided.Input Parameters
Output
Get Incremental Tickets (Cursor)
Get Incremental Tickets (Cursor)
ZENDESK_GET_INCREMENTAL_TICKETS_CURSORExport tickets incrementally using cursor-based pagination for synchronization, backups, or analytics. Supply a start time for the initial request and use the returned cursor in subsequent requests to fetch further pages.Input Parameters
Output
Get Incremental Users
Get Incremental Users
ZENDESK_GET_INCREMENTAL_USERSRetrieve users that have been modified since a specified start time using the Incremental User Export API. Use when you need to sync or track changes to Zendesk users over time, such as for data warehousing, backup, or external system synchronization. Provide a start_time (Unix timestamp) and the API returns users that have been created, updated, or deleted since that time. Call repeatedly with the end_time from each response to paginate through all changes. This action is read-only and idempotent. Note: Data isn’t available for the most recent minute due to eventual consistency. Users may appear as modified or deleted; interpret based on your use case.Input Parameters
Output
Incremental User Export (Cursor)
Incremental User Export (Cursor)
ZENDESK_GET_INCREMENTAL_USERS_CURSORExport users incrementally using cursor-based pagination. Use when you need to export all users from Zendesk in a reliable, paginated manner. The start_time parameter is required for the initial request to define the time range. Subsequent requests use the cursor returned in previous responses to fetch the next batch of records. This action is ideal for: - Full user data synchronization to external systems - Regular incremental backups of user data - Building user directories with pagination support Note: Data from the most recent minute is not included to ensure consistency.Input Parameters
Output
List Job Statuses
List Job Statuses
ZENDESK_GET_JOB_STATUSESList job statuses from Zendesk. Shows the status of all background jobs that have been initiated, including those created by bulk operations like bulk updates, imports, or exports. Each job status includes progress information, completion status, and any results from individual tasks. Use this action to track the progress of long-running operations or check if background tasks completed successfully. Use this action when you need to check the status of background jobs, monitor bulk operation progress, or verify that asynchronous tasks have finished processing.Input Parameters
Output
Get Job Status
Get Job Status
ZENDESK_GET_JOB_STATUSES2Get a single job status by ID from Zendesk. Shows the status of a background job initiated by bulk operations (like bulk updates, imports, or exports). The response includes progress information, completion status, and any results from individual tasks. Use this action when you have a job_status_id from a previously queued bulk operation and need to check if it completed successfully, failed, or is still processing. Check the ‘status’ field for the current state (‘queued’, ‘working’, ‘completed’, ‘failed’) and the ‘results’ array for individual task outcomes.Input Parameters
Output
Get Locale
Get Locale
ZENDESK_GET_LOCALEGet a locale by its ID or BCP-47 code. Use when you need to retrieve details about a specific locale including the locale identifier, language name, and timestamps.Input Parameters
Output
List Locales
List Locales
ZENDESK_GET_LOCALESList all translation locales available for your Zendesk account. Use when you need to retrieve the available locales for translation purposes, check which languages are enabled, or get locale metadata including the locale code, display name, and creation timestamps. This is a read-only, idempotent operation that supports pagination.Input Parameters
Output
List Agent Locales
List Agent Locales
Get Current Locale
Get Current Locale
Show Macro
Show Macro
ZENDESK_GET_MACRO2Show a specific macro by its ID. Use when you need to retrieve details of a single macro in your Zendesk account, such as for auditing, modifying, or understanding what actions and conditions are configured for a particular macro. Macros are saved response templates that agents can apply to tickets. Supports optional sideloads for usage statistics and additional metadata via the include parameter.Input Parameters
Output
List Macro Attachments
List Macro Attachments
ZENDESK_GET_MACRO_ATTACHMENTSList attachment metadata for a specific Zendesk macro, including filenames, content types, sizes, and download URLs. The response may include a next-page URL.Input Parameters
Output
List Macro Categories
List Macro Categories
List Macro Action Definitions
List Macro Action Definitions
ZENDESK_GET_MACRO_DEFINITIONSRetrieve the definitions of all actions that a macro can perform in Zendesk. Use this action when you need to discover what actions are available for macro creation, understand the available values for each action type, or build a macro configuration interface. The response includes action fields, their display titles, types, and available value options. Common macro actions include: setting ticket status, priority, or type; assigning agents or groups; adding/removing tags; setting custom fields; and adding comments.Output
Show Macro Replica
Show Macro Replica
ZENDESK_GET_MACRO_REPLICAShow a macro replica (unpersisted macro representation) based on a macro ID and ticket ID. Use when you need to preview how a macro will look when applied to a specific ticket, allowing you to see the actions and values that will be applied without actually applying the macro. This is useful for testing macro configurations or displaying macro previews in your interface. This action is read-only and idempotent.Input Parameters
Output
List Macros
List Macros
ZENDESK_GET_MACROSList all shared and personal macros available in your Zendesk account. Use when you need to retrieve, audit, or review the macros configured for automating ticket responses and actions. Macros are saved response templates that agents can apply to tickets. Supports filtering by access level, active status, category, and group. Results can be sorted by name, creation date, update date, or usage statistics.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
List Macro Actions
List Macro Actions
ZENDESK_GET_MACROS_ACTIONSList supported actions for macros in Zendesk. Use when you need to discover what field modifications are available when creating or editing macros. This endpoint returns the available action fields that can be set in a macro (e.g., status, priority, assignee, etc.) along with their possible values. This is useful for validating macro configurations or building macro management interfaces. This action is read-only and idempotent.Output
List Active Macros
List Active Macros
ZENDESK_GET_MACROS_ACTIVEList all active shared and personal macros in Zendesk. Use when you need to retrieve, audit, or review the macros configured in your Zendesk account. Macros are saved responses that agents can apply to tickets. This action supports filtering by access level, category, group, and sorting options. Note: This action only returns active macros. The sort_by parameter supports sorting by usage metrics (usage_1h, usage_24h, usage_7d, usage_30d) to identify the most frequently used macros.Input Parameters
Output
Show Changes to Ticket
Show Changes to Ticket
ZENDESK_GET_MACROS_APPLYShow changes to a ticket that would result from applying a macro. Use when you need to preview what changes a macro would make to a ticket before actually applying it. This allows you to review the changes that would be applied, such as assignee changes, group reassignments, comments, or custom field updates. This action is read-only and idempotent — it does not actually modify the ticket.Input Parameters
Output
Search Macros
Search Macros
ZENDESK_GET_MACROS_SEARCHSearch for Zendesk macros by their title. Use when you need to find macros in your Zendesk account by searching for keywords in their titles. Macros are pre-defined responses or actions that can be applied to tickets to automate repetitive tasks. This action supports filtering by access, active status, category, and group, as well as sorting results.Input Parameters
Output
Show Object Trigger
Show Object Trigger
ZENDESK_GET_OBJECT_TRIGGERShow a specific trigger for a custom object in Zendesk. Use when you need to retrieve details of a single trigger, such as for auditing, understanding its conditions and actions, or preparing modifications. This action is read-only and idempotent.Input Parameters
Output
List Open Requests
List Open Requests
Get Organization Field
Get Organization Field
ZENDESK_GET_ORGANIZATION_FIELD2Get details for a specific organization field in Zendesk by its ID or key. Use this action when you need to retrieve detailed information about a single custom organization field, including its type, options, validation rules, and display settings. This is useful for understanding field configuration or before updating/deleting a field. Returns the complete organization field definition with all metadata.Input Parameters
Output
List Organization Fields
List Organization Fields
ZENDESK_GET_ORGANIZATION_FIELDSList Zendesk organization field definitions, with an optional page parameter and dynamic content resolution. The response includes pagination links.Input Parameters
page[size]=50&page[after]=cursor or page[before]=cursor. Traditional offset: page=2 (integer). Cannot mix formats.Output
Get Organization Membership
Get Organization Membership
ZENDESK_GET_ORGANIZATION_MEMBERSHIP2Get details for a specific organization membership by its ID. Use when you have an organization membership ID and need to retrieve the associated user, organization, and membership metadata. This action is read-only and idempotent - calling it multiple times with the same membership ID will return the same result.Input Parameters
Output
List Organization Requests
List Organization Requests
ZENDESK_GET_ORGANIZATION_REQUESTSList requests for a specific Zendesk organization. Use when you need to retrieve all requests associated with a particular organization. This action returns request details including subject, status, priority, requester, and timestamps. Pagination is available for large result sets.Input Parameters
Output
Autocomplete Organizations
Autocomplete Organizations
ZENDESK_GET_ORGANIZATIONS_AUTOCOMPLETESearch for Zendesk organizations using autocomplete. Use when you need to find organization suggestions based on a partial organization name for ticket creation, user assignment, or organization lookup. The name parameter is required - provide at least a few characters for meaningful autocomplete results. Returns organizations sorted by relevance.Input Parameters
field_id is provided, this specifies the type of the field. For example, if the field is on a ‘zen:user’, it references a field on a user.source parameter. Use this to filter results based on custom field values.Output
List Organization Merges
List Organization Merges
ZENDESK_GET_ORGANIZATIONS_MERGESList all organization merge operations for a specific organization in Zendesk. This action retrieves the merge history showing which organizations were merged into or out of the specified organization. Use this action when you need to audit organization merge history or track the consolidation of organizations. Supports pagination to handle large result sets efficiently. This is a read-only, idempotent operation.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor. These are mutually exclusive.Output
Show Many Organizations
Show Many Organizations
ZENDESK_GET_ORGANIZATIONS_SHOW_MANYShow many Zendesk organizations by their IDs or external IDs. Use when you need to retrieve multiple organizations in a single API call. Accepts up to 100 organization IDs or external IDs as comma-separated lists. Only one of ids or external_ids should be provided. Returns organization objects with all standard fields including name, domain_names, tags, and organization_fields.Input Parameters
Output
Count Organization Tickets
Count Organization Tickets
ZENDESK_GET_ORGANIZATIONS_TICKETS_COUNTCount organization tickets in Zendesk. Returns an approximate count of tickets for a specific organization. Use when you need to know how many tickets are associated with an organization for reporting or operational purposes.Input Parameters
Output
Get Organization Subscription
Get Organization Subscription
ZENDESK_GET_ORGANIZATION_SUBSCRIPTIONShow Organization Subscription - retrieves details of a specific organization subscription by its ID. Use when you need to get information about an organization subscription, including the associated user and organization IDs, and the creation timestamp. This is a read-only operation that does not modify any data.Input Parameters
Output
List Organization Subscriptions
List Organization Subscriptions
ZENDESK_GET_ORGANIZATION_SUBSCRIPTIONSList Organization Subscriptions in Zendesk. Returns organization subscriptions with pagination support (cursor and offset). Use when you need to retrieve all organization subscriptions or need to paginate through results. End users only see their own subscriptions.Input Parameters
Output
Get Organization Tickets
Get Organization Tickets
ZENDESK_GET_ORGANIZATION_TICKETSGet tickets for a specific Zendesk organization, potentially including tickets from multiple requesters. Supports offset pagination and sorting; the page parameter is limited to 100.Input Parameters
Output
List Organization Users
List Organization Users
ZENDESK_GET_ORGANIZATION_USERSList users associated with a specific Zendesk organization. Supports filtering by role, permission set, or external ID, and pagination by page number.Input Parameters
Output
Count Organization Users
Count Organization Users
ZENDESK_GET_ORGANIZATION_USERS_COUNTCount users in a specific Zendesk organization by ID. Returns an approximate count of users. Use when you need to know how many users belong to a particular organization for reporting or operational purposes.Input Parameters
Output
Get Owned Apps
Get Owned Apps
ZENDESK_GET_OWNED_APPSList apps owned by the current Zendesk account. Use when you need to retrieve information about apps installed in your Zendesk instance, such as checking installed apps, reviewing app details (version, status, author), or auditing your app inventory. This endpoint requires admin authentication.Input Parameters
Output
List Ticket Problems
List Ticket Problems
ZENDESK_GET_PROBLEMSList Zendesk ticket problems. Use when you need to retrieve all tickets of type ‘problem’ in your Zendesk account. The response is always ordered by updated_at by default; use sort_by and sort_order parameters to customize. Supports both offset and cursor-based pagination. Note: Problems are tickets with type=‘problem’. This endpoint specifically returns problem-type tickets which are linked to other incidents that share the same root cause.Input Parameters
- for descending order. Common values: updated_at, created_at, id.Output
List Public Locales
List Public Locales
ZENDESK_GET_PUBLIC_LOCALESList all available public locales that can be used for translations in Zendesk. Use when you need to enumerate supported languages/locales for your Zendesk account, display language options to users, or determine which locales are available for ticket or article translations. This is a read-only, idempotent operation that returns the complete list of public locales with no pagination parameters.Output
Get Recent Tickets
Get Recent Tickets
ZENDESK_GET_RECENT_TICKETSList recently viewed tickets in Zendesk. Returns tickets sorted by the time they were last viewed, most recent first. Useful for agents to quickly access tickets they’ve been working on. The endpoint returns tickets visible to the agent based on their permission restrictions. Pagination is limited to 10,000 records (100 pages * 100 per page). Use this action to retrieve the tickets an agent has recently accessed in the Zendesk interface.Input Parameters
Output
List Remote Authentications
List Remote Authentications
ZENDESK_GET_REMOTE_AUTHENTICATIONSList all remote authentication configurations in your Zendesk account. Use this action when you need to enumerate SSO configurations, check which authentication methods are enabled, or retrieve metadata about remote authentication settings for agents and end users. This is a read-only, idempotent operation that returns all configured remote authentication providers including SAML, LDAP, JWT, and OAuth configurations.Output
List Request Comments
List Request Comments
ZENDESK_GET_REQUEST_COMMENTSList a page of comments on a Zendesk request, with optional time and author-role filters. The response includes pagination information and may include comment content, attachments and metadata.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). Mutually exclusive.Output
List CCD Requests
List CCD Requests
ZENDESK_GET_REQUESTS_CCDBList CCD Requests. Use when you need to retrieve requests where the authenticated end user is listed as a CC (carbon copy) recipient. These are requests the user is watching but did not create. Supports sorting by creation or update timestamps.Input Parameters
Output
Get Request Comment
Get Request Comment
Search Requests
Search Requests
ZENDESK_GET_REQUESTS_SEARCHSearch for requests in Zendesk using query syntax. Use when you need to find customer requests across Zendesk using flexible search criteria such as status, priority, subject, or requester information. Returns paginated results with request details. This action is read-only and idempotent - searching for requests does not modify any data.Input Parameters
Output
List Solved Requests
List Solved Requests
ZENDESK_GET_REQUESTS_SOLVEDList Zendesk requests with the ‘solved’ status. Useful for reviewing completed customer requests, generating reports on resolution times, or tracking customer satisfaction. Use this action when you need to retrieve requests that have been marked as solved.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
Get Agent Attribute Values
Get Agent Attribute Values
List Satisfaction Ratings
List Satisfaction Ratings
ZENDESK_GET_SATISFACTION_RATINGSList Zendesk ticket satisfaction ratings for reviewing customer feedback and CSAT scores. Supports page-number pagination and sorting.Input Parameters
?page=2 (integer page number) - Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before) These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering. Example: ?sort=name or ?sort=-created_atOutput
Count Satisfaction Ratings
Count Satisfaction Ratings
Get Search Results Count
Get Search Results Count
ZENDESK_GET_SEARCH_COUNTCount the number of items matching a search query in Zendesk. Use when you need to know how many results a search would return without fetching all the actual results. This is useful for displaying result counts before executing a full search.Input Parameters
Output
Export Search Results
Export Search Results
ZENDESK_GET_SEARCH_EXPORTExport Zendesk search results in batches using cursor pagination. Use the response’s after_cursor value as page_after to fetch the next page.Input Parameters
Output
Get Security Settings
Get Security Settings
ZENDESK_GET_SECURITY_SETTINGSShow Security Settings for a Zendesk account. Use when you need to retrieve the security configuration of a Zendesk account, including session timeouts, password policies, two-factor authentication settings, IP restrictions, and account assumption options. This is a read-only, idempotent operation that does not modify any data. This action is useful for auditing security settings, verifying compliance requirements, or understanding the security posture of a Zendesk account.Output
List Side Conversation Events
List Side Conversation Events
ZENDESK_GET_SIDE_CONVERSATIONS_EVENTSRetrieve side conversation events for incremental export. Returns events created since the specified start_time in chronological order. Use when you need to export or sync side conversation events for backup, analytics, or integration purposes. This action supports pagination via the next_page URL which contains a next_start_time parameter — pass that timestamp as start_time for subsequent requests. Only available to Admins. Note: This is a read-only, idempotent action suitable for building event pipelines or audit trails.Input Parameters
Output
Get Support Address
Get Support Address
Show Target
Show Target
ZENDESK_GET_TARGETShow a specific target by its ID. Use when you have a target ID and need to retrieve its details including title, type, active status, and creation timestamp. This is a read-only, idempotent operation that returns a single target object. This action is irreversible for data retrieval - it only reads target information, no destructive changes occur.Input Parameters
Output
Show Target Failure
Show Target Failure
ZENDESK_GET_TARGET_FAILUREShow a target failure in Zendesk. Use when you have a target_failure_id and need to retrieve details about a failed target execution, including the HTTP status code, raw request/response data, and consecutive failure count. This is a read-only operation.Input Parameters
Output
List Target Failures
List Target Failures
ZENDESK_GET_TARGET_FAILURESList the 25 most recent target failures in Zendesk. Target failures occur when a target (webhook, callback, or external integration) fails to execute properly. Each failure record includes the request sent, response received, and status code. Use this action to monitor and troubleshoot failing integrations.Output
List Targets
List Targets
ZENDESK_GET_TARGETSList all targets for the current Zendesk account. Use when you need to retrieve, audit, or review the targets configured in your Zendesk account. Targets are endpoints that receive data when triggers or automations fire. This is a read-only, idempotent action with no required parameters.Input Parameters
Output
Get Ticket Audit
Get Ticket Audit
List Ticket Collaborators
List Ticket Collaborators
ZENDESK_GET_TICKET_COLLABORATORSList all collaborators (CC’d users) on a Zendesk ticket. Use when you need to see who is currently CC’d on a ticket, such as when coordinating with multiple stakeholders or before adding/removing collaborators. Each collaborator is a user object with basic profile information. Paginate through results using page and per_page parameters.Input Parameters
Output
Get Ticket Comments
Get Ticket Comments
ZENDESK_GET_TICKET_COMMENTSList comments on a Zendesk ticket, including available author, content and attachment details. Supports sort order, page size and inclusion of inline images; comment body fields may be absent.Input Parameters
?include=users. Note: If the comment source is email, a deleted user will be represented as the CC’d email address. If the comment source is anything else, a deleted user will be represented as the user name.Output
List Ticket Email CCs
List Ticket Email CCs
Show Ticket Field
Show Ticket Field
ZENDESK_GET_TICKET_FIELD2Show a specific ticket field by its ID. Use when you need to retrieve details of a single ticket field in your Zendesk account, such as for auditing, understanding field configuration, or validating field properties. This action is read-only and idempotent.Input Parameters
creator_user_id and creator_app_name properties. If the ticket field is created by an app, creator_app_name is the name of the app and creator_user_id is -1. If the ticket field is not created by an app, then creator_app_name is nullOutput
List Ticket Fields
List Ticket Fields
ZENDESK_GET_TICKET_FIELDSList all system and custom ticket fields in Zendesk. Use when you need to retrieve field definitions for building forms, validating field values, or understanding available ticket field structure. Supports cursor-based pagination for large datasets. When creator=true is specified, includes creator_user_id and creator_app_name for each field. Locale parameter affects dynamic content variants for title_in_portal.Input Parameters
Output
Count Ticket Fields
Count Ticket Fields
Show Many Ticket Fields
Show Many Ticket Fields
ZENDESK_GET_TICKET_FIELDS_SHOW_MANYRetrieve multiple ticket fields by their IDs or keys in a single request. Use when you have specific ticket field identifiers (numeric IDs like ‘123’ or keys like ‘priority’, ‘status’, ‘subject’) and need to fetch their complete metadata including type, title, required status, custom options, and portal visibility settings. This is a read-only, idempotent operation. Up to 100 fields can be retrieved per request. Either ids or keys parameter can be used, but not both simultaneously.Input Parameters
ids or keys can be used, but not both.ids or keys can be used, but not both.Output
List Ticket Followers
List Ticket Followers
ZENDESK_GET_TICKET_FOLLOWERSList all followers on a Zendesk ticket. Use when you need to see who is following a ticket, such as when coordinating with stakeholders or managing ticket notifications. Followers receive notifications about the ticket. Each follower is a user object with basic profile information. Paginate through results using page and per_page parameters.Input Parameters
Output
List Ticket Forms
List Ticket Forms
ZENDESK_GET_TICKET_FORMSList Zendesk ticket forms and their metadata, with filters for active status, end-user visibility, form type, and brand association. Supports page and per-page pagination.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering. Example: ?sort=name or ?sort=-created_atOutput
Show Many Ticket Forms
Show Many Ticket Forms
ZENDESK_GET_TICKET_FORMS_SHOW_MANYShow multiple ticket forms by their IDs. Use when you need to retrieve specific ticket forms by their IDs to display form details, validate form availability, or bulk fetch form configurations. The ids parameter accepts a comma-separated list of ticket form IDs (e.g., ‘1,2,3’). Returns an empty ticket_forms array for non-existent IDs without error. Supports optional filtering by active status, end-user visibility, brand association, and default form fallback behavior.Input Parameters
has_more indicator in the cursor pagination response meta. Only valid with cursor pagination (page_size, page[after], page[before]).Output
List Ticket Incidents
List Ticket Incidents
ZENDESK_GET_TICKET_INCIDENTSList incidents linked to a problem ticket in Zendesk. Use when you need to retrieve all incident tickets that share the same root cause as a problem ticket. Incidents are tickets of type ‘incident’ that are related to a problem ticket via the problem_id field. Supports both offset and cursor-based pagination.Input Parameters
Output
Get Ticket Metric
Get Ticket Metric
ZENDESK_GET_TICKET_METRICRetrieve a specific ticket metric from Zendesk by its ID. Use this action when you have a ticket_metric_id and need to fetch the detailed metrics for that ticket, including resolution times, wait times, reply times, and SLA breaches. This action is read-only and idempotent — fetching the same metric multiple times has no side effects.Input Parameters
Output
Get Ticket Metrics
Get Ticket Metrics
ZENDESK_GET_TICKET_METRICSList Zendesk ticket metric records, including response times, resolution times, and assignment statistics, for analyzing ticket performance. Supports sorting and cursor-based page requests with a page size of up to 100.Input Parameters
Output
List Ticket Audits
List Ticket Audits
ZENDESK_GET_TICKETS_AUDITSList audits for a specific Zendesk ticket, including events such as comments and changes. Supports offset and cursor pagination; retrieve subsequent pages to view the audit history.Input Parameters
Output
Count Ticket Audits
Count Ticket Audits
ZENDESK_GET_TICKETS_AUDITS_COUNTCount audits for a specific ticket in Zendesk. Returns an approximate count of audits associated with the specified ticket. Use when you need to know how many audit records exist for a ticket for reporting, analytics, or operational purposes.Input Parameters
Output
Count Ticket Comments
Count Ticket Comments
ZENDESK_GET_TICKETS_COMMENTS_COUNTCount comments on a Zendesk ticket. Returns an approximate count of comments added to the specified ticket. Use when you need to know how many comments exist on a ticket without fetching the full comment list, such as for reporting or determining if pagination is needed.Input Parameters
Output
Get Ticket Conversation Log
Get Ticket Conversation Log
ZENDESK_GET_TICKETS_CONVERSATION_LOGList conversation log events for a specific Zendesk ticket. Use this action when you need to retrieve the chronological history of interactions, comments, and activities on a ticket. The conversation log provides a comprehensive view of all events including comments, status changes, and other ticket activities. Supports cursor-based pagination for accessing large datasets.Input Parameters
Output
Count Zendesk Tickets
Count Zendesk Tickets
ZENDESK_GET_TICKETS_COUNTCount the number of tickets in Zendesk. Returns an approximate count of tickets with the timestamp of when the count was last calculated. This is a read-only, idempotent operation. Use when you need to know the total number of tickets for reporting, capacity planning, or operational purposes. Note that the count is approximate and may not reflect real-time changes. For detailed per-ticket information, use ZENDESK_LIST_ZENDESK_TICKETS instead.Output
List Ticket Skips
List Ticket Skips
ZENDESK_GET_TICKET_SKIPSList ticket skips for a specific ticket from Zendesk. Use when you need to retrieve all skip records associated with a particular ticket, such as when reviewing which agents skipped working on a ticket or analyzing skip patterns. This action is read-only and idempotent. It returns a list of skip records that include the reason for skipping, who skipped it, and when.Input Parameters
Output
Get Ticket SLA Policy Metrics
Get Ticket SLA Policy Metrics
Get Ticket Metrics
Get Ticket Metrics
ZENDESK_GET_TICKETS_METRICSGet ticket metrics from Zendesk for a specific ticket. Returns performance metrics including resolution times, agent and requester wait times, reply counts, station changes, and timestamps for key events. Use when you need to analyze ticket performance, SLA compliance, or agent productivity metrics.Input Parameters
Output
List Side Conversation Events
List Side Conversation Events
Show Trigger
Show Trigger
ZENDESK_GET_TRIGGERShow a specific trigger by its ID. Use when you need to retrieve details of a single trigger in your Zendesk account, such as for auditing, modifying, or understanding what actions and conditions are configured for a particular trigger. This is useful for reviewing business rules before making changes or understanding automation behavior. This action is read-only and idempotent.Input Parameters
Output
List Trigger Categories
List Trigger Categories
ZENDESK_GET_TRIGGER_CATEGORIESList all ticket trigger categories in your Zendesk account. Use when you need to retrieve, audit, or review the trigger category organization for your business rules and automations. Supports filtering with sort options (position, name, created_at, updated_at) and can include rule counts via the include parameter to show how many triggers are in each category.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
Show Trigger Category
Show Trigger Category
List Ticket Triggers
List Ticket Triggers
ZENDESK_GET_TRIGGERSList Zendesk ticket triggers, with optional active-status and category filters and sorting. The tool accepts a page value and per-page size for pagination.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
Get Ticket Trigger Definitions
Get Ticket Trigger Definitions
ZENDESK_GET_TRIGGERS_DEFINITIONSGet Ticket Trigger Action and Condition Definitions. Use when you need to discover the available actions and conditions that can be used to create or configure ticket triggers. This returns metadata about what types of automations are possible - the action definitions show what a trigger can do (e.g., set status to ‘solved’), while the condition definitions show what conditions can trigger it (e.g., when status is ‘open’). This is a read-only, idempotent operation that returns the available trigger definitions metadata.Output
Search Ticket Triggers
Search Ticket Triggers
ZENDESK_GET_TRIGGERS_SEARCHSearch for Zendesk ticket triggers by their title. Use when you need to find triggers in your Zendesk account by searching for keywords in their titles. Triggers are business rules that automatically perform actions when certain conditions are met on tickets. This action supports filtering by active status, sorting, and sideloading usage statistics. This is a read-only and idempotent action that queries existing triggers without making any changes.Input Parameters
Output
Get User
Get User
ZENDESK_GET_USERTool to fetch a single Zendesk user by numeric user_id. Use when you have a user ID from ticket payloads (requester_id, submitter_id, assignee_id, author_id) and need to enrich with full user details (name, email, role, organization_id, etc.).Input Parameters
Output
Get Full User Entitlements
Get Full User Entitlements
ZENDESK_GET_USER_ENTITLEMENTS_FULLTool to retrieve full entitlements for a Zendesk user across all products (Chat, Explore, Talk, Guide). Use when you need to check which Zendesk products a user has access to and their activation status. Returns detailed entitlement information including whether each product is active and its display name.Input Parameters
Output
Get User Events
Get User Events
ZENDESK_GET_USER_EVENTSRetrieve event history for a specific Zendesk user. Use when you need to track user activity such as login history, profile changes, or other interactions with the Zendesk system. Supports filtering by event source, type, and time range. This action is read-only and idempotent. Note: The ‘zendesk’ source value is protected; attempts to use it when creating events result in an error.Input Parameters
Output
Get User Field By ID
Get User Field By ID
ZENDESK_GET_USER_FIELD_BY_IDRetrieve a single Zendesk user field by its numeric ID. Use when you have a user field ID and need to fetch its full definition including title, type, description, custom options, validation patterns, and other settings. This is a read-only, idempotent operation.Input Parameters
Output
List User Field Options
List User Field Options
ZENDESK_GET_USER_FIELD_OPTIONSList custom user field options for a given user field. Use when you need to retrieve the dropdown or tag options available for a custom user field in Zendesk. This action fetches the configurable options that can be selected for custom user fields of type dropdown, tagger, or similar multi-option field types.Input Parameters
Output
List User Fields
List User Fields
ZENDESK_GET_USER_FIELDSList custom user field definitions configured in a Zendesk account, including field types, dropdown options, and validation patterns. Results are paginated; use the pagination parameters to retrieve additional pages.Input Parameters
Output
Get User Fields Show Many
Get User Fields Show Many
ZENDESK_GET_USER_FIELDS_SHOW_MANYRetrieve multiple Zendesk user fields by their keys. Use when you have specific user field keys and need to fetch their definitions (title, type, description, options, etc.) in a single request instead of making individual calls. This is a read-only, idempotent operation.Input Parameters
Output
Get User Profile by Profile ID
Get User Profile by Profile ID
ZENDESK_GET_USER_PROFILES2Retrieve a single Zendesk user profile by its Sunshine profile ID. Use this action when you have a specific profile_id (obtained from profile listings or search results) and need to fetch the full profile details including attributes, identifiers, and linked user information. Note that this uses the Sunshine Profiles API with string profile IDs, not numeric user IDs from the Users API.Input Parameters
Output
Get User Profile Events by ID
Get User Profile Events by ID
ZENDESK_GET_USER_PROFILES_EVENTS2Get a page of events for a Sunshine profile by its profile ID, with optional source, type, and time filters. Use it to examine profile activity or event history.Input Parameters
Output
Get User's Assigned Tickets
Get User's Assigned Tickets
ZENDESK_GET_USERS_ASSIGNED_TICKETSList tickets assigned to a specified Zendesk user, with sorting and offset pagination. The page parameter is limited to pages 1–100.Input Parameters
Output
Autocomplete Users
Autocomplete Users
ZENDESK_GET_USERS_AUTOCOMPLETEAutocomplete users by name or phone number. Use when you need to find users based on a partial name or phone number for ticket creation or user lookup scenarios. At least one of ‘name’ or ‘phone’ must be provided.Input Parameters
Output
List Brand Agent Memberships By User
List Brand Agent Memberships By User
ZENDESK_GET_USERS_BRAND_AGENTSList brand agent memberships for a specific user in Zendesk. Use when you have a user ID and need to find all brands that the user is an agent for, such as auditing which brands a specific agent can access. This is a read-only, idempotent operation.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
Get User's CC'd Tickets
Get User's CC'd Tickets
ZENDESK_GET_USERS_CCD_TICKETSList tickets where a specified Zendesk user is CC’d, with sorting and offset pagination. The page parameter is limited to pages 1–100.Input Parameters
Output
Get User Compliance Deletion Statuses
Get User Compliance Deletion Statuses
ZENDESK_GET_USERS_COMPLIANCE_DELETION_STATUSESTool to fetch GDPR compliance deletion statuses for a specific Zendesk user. Use when you need to check the deletion status for each compliance area (e.g., chat, talk) associated with a user account. Returns status records showing deletion requests and their current state. Use when auditing user data deletion requests, verifying GDPR compliance status, or tracking the progress of data removal across different Zendesk products.Input Parameters
Output
Count Users
Count Users
ZENDESK_GET_USERS_COUNTCount users in Zendesk. Returns an approximate count of users. If the count is more than 1000, the value is an estimate and the response is refreshed every 24 hours. Use when you need to know how many users exist in the system for reporting or administrative purposes.Input Parameters
Output
List User Sessions
List User Sessions
ZENDESK_GET_USER_SESSIONSList all sessions for a specific Zendesk user. Returns details about each active session including authentication time and last seen time. Use this action to monitor session activity for a specific user, investigate security events, or audit login history for account troubleshooting. Use when you need to see all active sessions for a particular user, track their login activity, or investigate potential unauthorized access.Input Parameters
- for descending order. Example: ?sort=created_at or ?sort=-created_atOutput
Get User's Followed Tickets
Get User's Followed Tickets
ZENDESK_GET_USERS_FOLLOWED_TICKETSList tickets the specified Zendesk user is following. Returns all tickets where the specified user is a follower. Use when you need to retrieve all tickets a particular user is watching or tracking, such as for notification purposes, audit trails, or understanding which tickets a user has interest in. Pagination is available for large result sets; follow next_page links until null to retrieve all followed tickets.Input Parameters
Output
List Memberships By User
List Memberships By User
ZENDESK_GET_USERS_GROUP_MEMBERSHIPSList group memberships for a specific Zendesk user. Use when you need to retrieve all groups a user belongs to, audit user group assignments, or understand which support groups a specific user is a member of. This action is read-only and idempotent. Supports both offset pagination (page, per_page) and cursor pagination (page_size, page_after, page_before). Also supports sideloading users and groups via the include parameter.Input Parameters
- for descending order. Example: ?sort=group_id or ?sort=-created_atusers, groups.Output
Get User's Group Membership
Get User's Group Membership
ZENDESK_GET_USERS_GROUP_MEMBERSHIPS_BY_IDGet a specific group membership for a user by their IDs. Use when you have both a user ID and a group membership ID and need to retrieve details including the associated group, user, and timestamps. This action retrieves a single group membership record scoped to a specific user, unlike GetGroupMembership which retrieves by membership ID alone, and unlike ListUsersGroupMemberships which lists all memberships for a user.Input Parameters
Output
List User Groups
List User Groups
ZENDESK_GET_USERS_GROUPSList groups a specific Zendesk user belongs to, with page and per-page parameters, optional exclusion of deleted groups, and sorting. Use it to audit team memberships or retrieve a user’s support groups.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor. These are mutually exclusive.- for descending order. Example: ?sort=name or ?sort=-created_athas_more indicator in the cursor pagination response meta. Only valid with cursor pagination (page[size], page[after], page[before]).Output
Count User Groups
Count User Groups
ZENDESK_GET_USERS_GROUPS_COUNTCount user groups in Zendesk. Returns an approximate count of groups that a specific user belongs to. Use when you need to know how many groups a user is assigned to for reporting, organizational management, or operational purposes. This action is read-only and idempotent.Input Parameters
Output
Show User Identity
Show User Identity
ZENDESK_GET_USERS_IDENTITIES2Tool to show a specific user identity by user ID and identity ID. Use when you need to retrieve detailed information about a particular identity associated with a Zendesk user. This action is read-only and idempotent - it only retrieves data without modifying anything.Input Parameters
Output
Get Current Session
Get Current Session
ZENDESK_GET_USERS_ME_SESSIONRetrieve sessions for the currently authenticated Zendesk user, with optional pagination. Session details can include authentication time, last seen time, and user ID.Input Parameters
?page[size]=50&page[after]=cursor (deepObject with size/after/before). Most callers don’t need this — current users typically have only a handful of sessions.Output
Get Current User Settings
Get Current User Settings
ZENDESK_GET_USERS_ME_SETTINGSGet the settings for the currently authenticated user in Zendesk. Returns user preferences including Admin Center UI settings, Lotus UI settings (onboarding, tooltips, keyboard shortcuts), and shared views order. Use this action to retrieve the current user’s personal settings and preferences.Output
List User Organization Memberships
List User Organization Memberships
ZENDESK_GET_USERS_ORGANIZATION_MEMBERSHIPSList organization memberships for a specific Zendesk user. Returns membership details including default status, ticket viewing permission, and organization information; the response may contain a next-page URL.Input Parameters
Output
Get User's Organization Membership
Get User's Organization Membership
ZENDESK_GET_USERS_ORGANIZATION_MEMBERSHIPS2Get details for a specific organization membership by user ID and membership ID. Use when you have both a user ID and an organization membership ID and need to retrieve the associated membership metadata including organization details, default status, and ticket viewing permissions. This action is read-only and idempotent - calling it multiple times with the same parameters will return the same result.Input Parameters
Output
List User Organizations
List User Organizations
ZENDESK_GET_USERS_ORGANIZATIONSList organizations associated with a specific Zendesk user. Returns a page of organization details, including name, domain names, tags, and custom fields, with pagination options.Input Parameters
Output
Get User's Organizations Count
Get User's Organizations Count
List User's Organization Subscriptions
List User's Organization Subscriptions
ZENDESK_GET_USERS_ORGANIZATION_SUBSCRIPTIONSList User’s Organization Subscriptions - retrieves organization subscriptions for a specific user. Use when you need to get all organization subscriptions associated with a particular user, including the organization IDs and creation timestamps. Supports both cursor and offset pagination. End users only see their own subscriptions. This is a read-only operation that does not modify any data.Input Parameters
Output
Get User Password Requirements
Get User Password Requirements
ZENDESK_GET_USERS_PASSWORD_REQUIREMENTSGet password requirements for a specific Zendesk user. Use when you need to retrieve the password policy rules that apply to a user’s password, such as minimum length, complexity requirements, or expiration policies. This action is read-only and idempotent.Input Parameters
Output
Get Users Profiles
Get Users Profiles
ZENDESK_GET_USERS_PROFILESRetrieve profiles associated with a specific Zendesk user by user ID. Use when you need to look up user profile information using the Zendesk user ID. This action returns all profiles linked to the specified user account. This action is read-only and idempotent. Note: Access requires agent permissions in Zendesk (Support > People > Roles > People).Input Parameters
Output
Get User's Requested Tickets
Get User's Requested Tickets
ZENDESK_GET_USERS_REQUESTED_TICKETSList tickets requested by a specified Zendesk user, with sorting and offset pagination. The page parameter is limited to pages 1–100.Input Parameters
Output
List User Requests
List User Requests
ZENDESK_GET_USERS_REQUESTSList ticket requests for a specific Zendesk user. Use when you need to retrieve all requests associated with a particular user ID. This is useful for viewing a user’s request history or monitoring their open tickets. This action is read-only and idempotent.Input Parameters
Output
List User Skips
List User Skips
ZENDESK_GET_USERS_SKIPSList ticket skips for a specific user from Zendesk. Use when you need to retrieve all skip records associated with a particular user, such as when analyzing which tickets a user has skipped or reviewing their skip history. This action is read-only and idempotent. Note that archived tickets are not included in the results.Input Parameters
Output
Count User Assigned Tickets
Count User Assigned Tickets
ZENDESK_GET_USER_TICKETS_ASSIGNED_COUNTCount tickets assigned to a specific user in Zendesk. Returns an approximate count of tickets where the user is the assignee. Use when you need to know how many tickets are currently assigned to a particular user for workload analysis, reporting, or capacity planning. Note: The count is approximate and may not reflect real-time changes. The count is refreshed periodically rather than being calculated on every request.Input Parameters
Output
List View Filter Definitions
List View Filter Definitions
List Views
List Views
ZENDESK_GET_VIEWSList shared and personal Zendesk views available to the current user, with access, active-status, and group filters. Supports page-number pagination and sorting.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
List Active Views
List Active Views
ZENDESK_GET_VIEWS_ACTIVEList all active shared and personal views available in Zendesk. Use when you need to retrieve, audit, or present the view configuration in your Zendesk account. Views define how tickets are filtered, grouped, and displayed to agents. Supports filtering by access type (personal, shared, account), group membership, and sorting preferences.Input Parameters
Output
List Views - Compact
List Views - Compact
ZENDESK_GET_VIEWS_COMPACTRetrieves a compacted list of shared and personal views available to the current user in Zendesk. Use when you need to quickly fetch a lightweight list of views without full details. This endpoint returns essential view information suitable for dropdown menus or quick selection lists. Unlike the standard /views endpoint, this compact version provides a streamlined response with the most commonly needed fields.Output
Count Views
Count Views
Count Tickets in Views
Count Tickets in Views
ZENDESK_GET_VIEWS_COUNT_MANYCount tickets in multiple Zendesk views. Returns the ticket count for each view ID provided in a single API call. Use when you need to quickly get counts for multiple views at once for reporting or dashboard purposes. Note: This is a read-only, idempotent operation. Counts may be cached on the server side.Input Parameters
Output
Execute View
Execute View
ZENDESK_GET_VIEWS_EXECUTEExecute a Zendesk view to retrieve its column titles and matching ticket rows. Use when you need to run a saved view and get its results - useful for checking which tickets match a view’s conditions without manually applying filters. Supports pagination, custom sorting, and optional grouping of results. Returns the view’s execution metadata alongside the matching rows.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
Export View
Export View
ZENDESK_GET_VIEWS_EXPORTRequest an export of a specified Zendesk view and return the response as a downloadable file, along with the view ID and content type.Input Parameters
Output
Search Views
Search Views
ZENDESK_GET_VIEWS_SEARCHSearch for Zendesk views by their title. Use when you need to find views in your Zendesk account by searching for keywords in their titles. Views are saved searches that display tickets matching specific conditions. This action supports filtering by access level, active status, group, and sorting results.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). Mutually exclusive.Output
List Views By IDs
List Views By IDs
ZENDESK_GET_VIEWS_SHOW_MANYGet multiple Zendesk views by their IDs. Use when you need to retrieve specific views by their IDs in a single request rather than fetching them one by one. The IDs should be provided as a comma-separated string. This action is read-only and idempotent. Returns only views that exist and for which the user has permission.Input Parameters
Output
List Tickets From View
List Tickets From View
ZENDESK_GET_VIEWS_TICKETSList tickets from a specific Zendesk view, with optional sorting and cursor pagination. This read-only action can be used to analyze tickets matching the view’s conditions; retrieve additional pages as needed.Input Parameters
Output
Count Tickets in View
Count Tickets in View
ZENDESK_GET_VIEW_TICKET_COUNTCount tickets in a specific view in Zendesk. Returns the number of tickets matching the view’s conditions. Use when you need to know how many tickets are in a particular view for reporting, routing decisions, or workload assessment. The count may be null if the system is still loading and caching new data. This action is read-only and idempotent.Input Parameters
Output
List Activities
List Activities
ZENDESK_GET_ZENDESK_ACTIVITIESList ticket activities in the last 30 days affecting your Zendesk. Activities include actions like ticket assignments, status changes, comments, and more. This action is read-only and idempotent — use it to monitor ticket activity or build activity feeds.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive.- for descending order. Example: ?sort=name or ?sort=-created_atOutput
List Custom Roles
List Custom Roles
ZENDESK_GET_ZENDESK_CUSTOM_ROLESList all custom roles configured in your Zendesk account. Use when you need to discover available roles, review role configurations, or understand permission structures for your agents. Returns metadata including role names, descriptions, role types, and permission configurations. This is a read-only, idempotent operation with no required parameters.Output
Get Zendesk Organization
Get Zendesk Organization
ZENDESK_GET_ZENDESK_ORGANIZATIONGet metadata for a specific Zendesk organization by ID. Response fields are available under data.organization_info. Does not return member/user lists.Input Parameters
Output
Get Zendesk Organization Merge
Get Zendesk Organization Merge
ZENDESK_GET_ZENDESK_ORGANIZATION_MERGERetrieve the details of a specific organization merge operation in Zendesk. This action shows the merge status and the organizations involved. Use when you need to check the status of an organization merge or view details of a past merge operation. This is a read-only, idempotent operation.Input Parameters
Output
List Organization Subscriptions
List Organization Subscriptions
ZENDESK_GET_ZENDESK_ORGANIZATIONS_SUBSCRIPTIONSList organization subscriptions for a specific Zendesk organization, linking users to the organization. This read-only action returns a page of subscriptions with pagination information; page numbers are limited to 100.Input Parameters
Output
List Requests
List Requests
ZENDESK_GET_ZENDESK_REQUESTSList a page of Zendesk ticket requests, with sorting by creation or update time. This action is read-only and idempotent.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.Output
List Sessions
List Sessions
ZENDESK_GET_ZENDESK_SESSIONSList all active sessions in your Zendesk account. If authenticated as an admin, returns all the active sessions for all users. Otherwise, returns only the sessions for the authenticated user. Use this action to monitor active user sessions, track login activity, or manage session security. Use when you need to audit active user sessions, investigate security events, or retrieve session information for user activity monitoring.Input Parameters
- for descending order. When used with cursor pagination, this determines the cursor ordering. Example: ?sort=name or ?sort=-created_atOutput
List Sharing Agreements
List Sharing Agreements
ZENDESK_GET_ZENDESK_SHARING_AGREEMENTSList all sharing agreements for your Zendesk account. Sharing agreements define connections between Zendesk accounts for sharing tickets. This action is read-only and idempotent — use it to view current sharing relationships or check agreement status.Output
List Suspended Tickets
List Suspended Tickets
ZENDESK_GET_ZENDESK_SUSPENDED_TICKETSList suspended tickets in Zendesk. Suspended tickets are tickets that were automatically held for review due to spam detection, banned content, or other filtering rules. This action is read-only and idempotent — use it to review suspended tickets and determine if they should be recovered or deleted.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive — use one format or the other, not both.Output
Get Zendesk Ticket
Get Zendesk Ticket
ZENDESK_GET_ZENDESK_TICKET_BY_IDGet a Zendesk ticket’s selected details and a page of its comments, including available attachments. Comment pagination can be controlled by page and per-page parameters; comment fields and ticket properties may be null.Input Parameters
Output
List Ticket Field Options
List Ticket Field Options
ZENDESK_GET_ZENDESK_TICKET_FIELDS_OPTIONSList Ticket Field Options - Returns a list of custom ticket field options for dropdown and multi-select ticket fields. Use this action to retrieve the available choices users can select when filling out a custom ticket field. This action is read-only and idempotent. Note: Only works with dropdown, tagger, and multi-select custom ticket fields; standard fields like text or date do not have options.Input Parameters
Output
Show Ticket Field Option
Show Ticket Field Option
ZENDESK_GET_ZENDESK_TICKET_FIELDS_OPTIONS2Show Ticket Field Option - Retrieves a specific custom ticket field option for dropdown and multi-select ticket fields. Use this action when you have a ticket_field_id and a ticket_field_option_id and need to retrieve the details of that individual option. This action is read-only and idempotent. Note: Only works with dropdown, tagger, and multi-select custom ticket fields; standard fields like text or date do not have options.Input Parameters
Output
Get Zendesk Ticket Form
Get Zendesk Ticket Form
ZENDESK_GET_ZENDESK_TICKET_FORMGet details for a specific ticket form in Zendesk by its ID. Returns the complete ticket form object including its name, display settings, visibility conditions, associated ticket fields, and brand restrictions. Use when you need to retrieve detailed information about a particular ticket form configuration. This is a read-only, idempotent operation that does not modify any data.Input Parameters
Output
Get Side Conversation
Get Side Conversation
List Active Automations
List Active Automations
List App Installations
List App Installations
List App Locations
List App Locations
List Assignable Group Memberships
List Assignable Group Memberships
ZENDESK_LIST_ASSIGNABLE_GROUP_MEMBERSHIPSList assignable group memberships in Zendesk. Use when you need to retrieve the group memberships that agents can be assigned to, typically for understanding agent-group assignments or building assignment interfaces. This action is read-only and idempotent. Returns a maximum of 100 group memberships per page.Input Parameters
Output
List Assignable Memberships By Group
List Assignable Memberships By Group
ZENDESK_LIST_ASSIGNABLE_GROUP_MEMBERSHIPS_BY_GROUPList assignable group memberships for a specific group in Zendesk. Use when you need to retrieve which agents can be assigned to a particular group, typically for building assignment interfaces or auditing group membership capabilities. This action is read-only and idempotent. Returns a maximum of 100 group memberships per page. Note: This action differs from ListAssignableGroupMemberships by filtering to a specific group rather than returning all assignable memberships.Input Parameters
Output
List Bookmarks
List Bookmarks
ZENDESK_LIST_BOOKMARKSList the user’s Zendesk bookmarks to find saved tickets or manage bookmarked items. Archived tickets are not included; results are paginated.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive.Output
List Brand Agent Memberships
List Brand Agent Memberships
ZENDESK_LIST_BRAND_AGENTSList brand agent memberships to retrieve which agents are associated with which brands in Zendesk. Use this action when you need to enumerate the brand-agent relationships in a Zendesk account, such as determining which agents can access specific brands or auditing brand access permissions. This is a read-only, idempotent operation.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
List Custom Object Record Attachments
List Custom Object Record Attachments
ZENDESK_LIST_CUSTOM_OBJECT_RECORD_ATTACHMENTSList all file attachments for a specific custom object record in Zendesk. Use this action when you need to retrieve the attachments associated with a particular custom object record, for example to display files, verify uploads, or manage attachments for a record. This is a read-only operation that retrieves attachment metadata without downloading file content.Input Parameters
Output
List Custom Object Records
List Custom Object Records
ZENDESK_LIST_CUSTOM_OBJECT_RECORDSList all records for a specific custom object type in Zendesk. Use this action when you need to retrieve all instances of a custom object (e.g., all car records, all product records) with optional filtering by ID, external ID, sorting, and pagination support. This is a read-only, idempotent operation that returns records with their custom field values. Note: When using pagination (page[size], page[after], page[before]), you cannot mix page[before] and page[after] in the same request.Input Parameters
Output
List Deleted Users
List Deleted Users
ZENDESK_LIST_DELETED_USERSTool to list deleted users in Zendesk via the Users API. Use when you need to retrieve information about users that have been deleted from the system. This is a read-only operation.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive.- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
List Help Center Content
List Help Center Content
List Incremental Custom Object Records
List Incremental Custom Object Records
ZENDESK_LIST_INCREMENTAL_CUSTOM_OBJECT_RECORDSExport custom object records incrementally using cursor-based pagination. Use this action when you need to retrieve all changes to custom object records since a specific time, with support for large result sets through cursor-based pagination. The start_time parameter is required for the initial request; subsequent pages use the cursor returned in previous responses. This is a read-only, idempotent operation that returns records with their custom field values and change timestamps. The action supports filtering to exclude deleted records and configurable page sizes. Rate limited to 10 requests per minute.Input Parameters
Output
List Monitored X Handles
List Monitored X Handles
List Object Triggers
List Object Triggers
ZENDESK_LIST_OBJECT_TRIGGERSList triggers for a specific Zendesk custom object, including their conditions and actions. Results are paginated and can be filtered by active status.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). Mutually exclusive.Output
List Object Trigger Definitions
List Object Trigger Definitions
ZENDESK_LIST_OBJECT_TRIGGERS_DEFINITIONSList Object Trigger Action and Condition Definitions for a custom object in Zendesk. Use when you need to discover the available trigger actions and conditions that can be used to create or configure triggers on a custom object. This returns metadata about what types of automations are possible for the specified custom object. This is a read-only, idempotent operation that returns the available trigger definitions.Input Parameters
Output
List Organization Memberships
List Organization Memberships
ZENDESK_LIST_ORGANIZATION_MEMBERSHIPSList organization memberships in Zendesk. Use when you need to retrieve all organization memberships, which link users to organizations. Supports pagination and sorting options to navigate large result sets efficiently.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor. These are mutually exclusive.- for descending order. Example: ?sort=name or ?sort=-created_atOutput
List Organization Memberships by Organization
List Organization Memberships by Organization
ZENDESK_LIST_ORGANIZATION_MEMBERSHIPS_BY_ORGANIZATIONList organization memberships for a specific Zendesk organization, including membership metadata such as default status and ticket viewing permissions. Supports pagination and sorting.Input Parameters
?page=2 (integer page number). Cursor: ?page[size]=50&page[after]=cursor. These are mutually exclusive.- for descending order. Example: ?sort=name or ?sort=-created_atOutput
List Resource Collections
List Resource Collections
ZENDESK_LIST_RESOURCE_COLLECTIONSList Resource Collections for the Zendesk account. Use when you need to retrieve, audit, or review the resource collections configured in your Zendesk account. Resource collections are groups of related resources that can be managed together. This is a read-only action that returns paginated results. Use per_page to control page size.Input Parameters
Output
List All Skips
List All Skips
ZENDESK_LIST_SKIPSLists all ticket skips in Zendesk. A skip is a ticket that was skipped during routing or assignment. Use this action to retrieve information about all tickets that have been skipped. This action is read-only and idempotent. Note that archived tickets are not included in the results.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive.Output
List Support Addresses
List Support Addresses
ZENDESK_LIST_SUPPORT_ADDRESSESList Zendesk support addresses, including their default status, verification status and brand associations. This read-only action accepts an offset page and per-page size, along with sorting and sideload parameters.Input Parameters
?page=2 (integer page number), cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). These are mutually exclusive - use one format or the other, not both.- for descending order. When used with cursor pagination, this determines the cursor ordering.Output
List Ticket Audits
List Ticket Audits
ZENDESK_LIST_TICKET_AUDITSList all ticket audits from Zendesk. Returns a paginated list of audit records, each containing events that describe changes made to tickets. Audits capture all changes including comments, status changes, assignments, and field updates. Archived tickets are not included in the results. Use cursor pagination (page_after, page_before, page_size) to navigate through results efficiently.Input Parameters
after_cursor value from a previous request. Note: page[before] and page[after] cannot be used together.before_cursor value from a previous request. Note: page[before] and page[after] cannot be used together.Output
List Ticket Content Pins
List Ticket Content Pins
ZENDESK_LIST_TICKET_CONTENT_PINSList Ticket Content Pins returns all content pins for a specified ticket. Use when you need to retrieve all pinned content items on a ticket. ticket_id is required — Zendesk has no account-wide listing mode. _tags = [“readOnlyHint”, “idempotentHint”]Input Parameters
Output
List User Identities
List User Identities
ZENDESK_LIST_USER_IDENTITIESTool to list all identities for a specific Zendesk user. Use when you need to retrieve all email addresses, phone numbers, or other contact methods associated with a user. Supports filtering by identity type and cursor-based pagination.Input Parameters
Output
List Access Rules
List Access Rules
ZENDESK_LIST_ZENDESK_ACCESS_RULESList all access rules for a Zendesk custom object. Access rules control which users and roles can perform specific operations on custom object records. Use this action when you need to audit existing permissions or understand what access controls are in place for a custom object type. This is a read-only operation.Input Parameters
Output
List Custom Object Fields
List Custom Object Fields
ZENDESK_LIST_ZENDESK_CUSTOM_OBJECT_FIELDSList field definitions for a Zendesk custom object. The request supports pagination and can include or exclude standard fields; each call returns the requested page.Input Parameters
?page=2 (integer page number); cursor uses ?page[size]=50&page[after]=cursor (deepObject with size, after, before). Mutually exclusive.Output
List Custom Objects
List Custom Objects
ZENDESK_LIST_ZENDESK_CUSTOM_OBJECTSList all custom object definitions in Zendesk. Use this action when you need to discover available custom object types, understand their structure, or retrieve metadata about custom objects for further operations. Returns metadata including keys, titles, and configuration options for each custom object.Input Parameters
Output
List Permission Policies
List Permission Policies
ZENDESK_LIST_ZENDESK_PERMISSION_POLICIESList all permission policies for a custom object in Zendesk. Use this action when you need to discover the access control configuration for a custom object, understand what roles have permissions, or retrieve permission metadata for access control management. This is a read-only, idempotent operation. This action is useful for reviewing permission policies applied to custom objects in Zendesk.Input Parameters
Output
List Tickets
List Tickets
ZENDESK_LIST_ZENDESK_TICKETSList Zendesk tickets with pagination and filtering. Only server-side filter available is external_id; status, priority, tags, assignee_id, and date-range filters must be applied client-side. Timestamps (created_at, updated_at) are ISO 8601 UTC. ticket.subject may be null — coerce to string before filtering. Attachments are not included; retrieve via ZENDESK_GET_ZENDESK_TICKET_BY_ID. HTTP 429 rate limit responses include Retry-After header; apply exponential backoff. Paginate by following next_page until null to avoid missing tickets.Input Parameters
Output
List Users
List Users
ZENDESK_LIST_ZENDESK_USERSTool to list/enumerate Zendesk users via the Users API. Use when you need to export or iterate through the user directory without a specific name/email filter. Supports both cursor and offset pagination.Input Parameters
Output
Make Zendesk Ticket Comment Private
Make Zendesk Ticket Comment Private
ZENDESK_MAKE_COMMENT_PRIVATEMake a public ticket comment private in Zendesk. This action changes the visibility of a comment from public to internal-only, so only agents can view it. Use this action when you need to convert a customer-facing comment to an internal note after the fact. Note: Only agents can make comments private; end users cannot use this endpoint.Input Parameters
Output
Make Organization Membership Default
Make Organization Membership Default
ZENDESK_MAKE_DEFAULT_ORGANIZATION_MEMBERSHIPSet a specific organization membership as the default for a user in Zendesk. Use when you need to change which organization is the primary/default for a user. Only one organization can be the default at a time. This action is idempotent - setting the same membership as default multiple times will succeed without side effects.Input Parameters
Output
Make End User Identity Primary
Make End User Identity Primary
ZENDESK_MAKE_END_USER_IDENTITY_PRIMARYSet a specified identity as the primary identity for an end user in Zendesk. This is a collection-level operation - after making an identity primary, you should reload the entire identities collection to get the updated state. An end user can only make an email identity primary if the email is verified. Use when a user wants to change their primary email or phone number for notifications.Input Parameters
Output
Make Ticket Comment Private
Make Ticket Comment Private
ZENDESK_MAKE_TICKET_COMMENT_PRIVATEChange a public comment to private on a Zendesk ticket audit. Use when you need to convert a previously public-facing comment to an internal note that is not visible to the end user. This action makes the comment private by updating the ticket audit. This is useful when information was shared publicly by mistake and needs to be restricted to agents only. Note: This action only works on existing audits and cannot be undone once the comment is made private.Input Parameters
Output
Make User Identity Primary
Make User Identity Primary
ZENDESK_MAKE_USER_IDENTITY_PRIMARYTool to set a user identity as the primary identity for a Zendesk user. Use when you need to change which email address or identifier is the primary contact method for a user. This action may affect which email notifications the user receives.Input Parameters
Output
Mark Multiple Tickets as Spam
Mark Multiple Tickets as Spam
ZENDESK_MARK_MANY_TICKETS_AS_SPAMMarks multiple tickets as spam in Zendesk. This action is irreversible — the tickets will be marked as spam and moved to the suspended tickets queue. The submitter will also be marked as spam and blocked from submitting further tickets. Use when cleaning up spam or unwanted tickets to protect your support queue. Returns a job_status payload for tracking the bulk operation. Note: Tickets marked as spam are moved to the suspended tickets queue and cannot be recovered through normal means.Input Parameters
Output
Merge Users
Merge Users
ZENDESK_MERGE_USERSMerges two Zendesk end users together. The user specified in the path parameter (user_id) is the primary user (target) that will be kept. The user specified in the request body (id) is the source user that will be deleted and its data transferred to the primary user. Use when you need to consolidate duplicate end-user accounts in Zendesk. This action is irreversible — the source user and all their associated data (tickets, comments, etc.) will be merged into the primary user and the source user cannot be recovered.Input Parameters
Output
Merge Zendesk Tickets
Merge Zendesk Tickets
ZENDESK_MERGE_ZENDESK_TICKETSMerges multiple tickets into a target ticket in Zendesk. The source tickets are merged into the target ticket and then deleted. This is an asynchronous operation that returns a job status. Use when you need to consolidate duplicate or related tickets into a single ticket. Important: This action is irreversible - source tickets are permanently merged and deleted once the operation completes. Always verify the target_ticket_id and source_ticket_ids before executing.Input Parameters
Output
Open User's Profile in Agent Browser
Open User's Profile in Agent Browser
ZENDESK_OPEN_USERS_PROFILE_IN_AGENT_BROWSEROpen a Zendesk user’s profile in a specified agent’s browser. Use when an agent needs to view a specific user’s profile during an active call or session. This action triggers the Zendesk Talk dashboard to display the user’s information in the agent’s interface.Input Parameters
Output
Recover Multiple Suspended Tickets
Recover Multiple Suspended Tickets
ZENDESK_RECOVER_MANY_SUSPENDED_TICKETSRecover multiple suspended tickets in Zendesk. Use when you need to restore tickets that have been suspended (e.g., auto-replied emails, bounced messages). Takes up to 100 ticket IDs as input and restores them to normal ticket status. This action is irreversible — recovered tickets return to normal processing.Input Parameters
Output
Renew Session
Renew Session
ZENDESK_RENEW_SESSIONRenew the current Zendesk session and obtain a new authenticity token. Use when the current session token is expiring or needs to be refreshed to maintain an active authenticated connection. This action extends the session lifetime without requiring full re-authentication.Output
Reorder Custom Object Fields
Reorder Custom Object Fields
ZENDESK_REORDER_CUSTOM_OBJECT_FIELDSReorder Custom Fields of an Object. Updates the display order of custom object fields based on the provided field IDs. Use when you need to change the order of fields displayed in a custom object’s record layout. This action is idempotent — re-running with the same field IDs in the same order will produce the same result.Input Parameters
Output
Reorder App Location Installations
Reorder App Location Installations
ZENDESK_REORDER_LOCATION_INSTALLATIONSReorder App Installations For Location. Creates or updates the relevant location installation with a specified installation order. This action requires admin-level access. Use when you need to change the display order of apps in a specific Zendesk location (e.g., nav bar, ticket sidebar).Input Parameters
Output
Reorder Organization Fields
Reorder Organization Fields
ZENDESK_REORDER_ORGANIZATION_FIELDSReorder Organization Fields. Updates the display order of organization fields based on the provided field IDs. Use when you need to change the order of organization fields displayed in Zendesk. This action is idempotent — re-running with the same field IDs in the same order will produce the same result.Input Parameters
Output
Reorder Ticket Fields
Reorder Ticket Fields
ZENDESK_REORDER_TICKET_FIELDSReorder Ticket Fields. Updates the display order of ticket fields based on the provided field IDs. Use when you need to change the order of standard ticket fields displayed in the ticket form. This action is idempotent — re-running with the same field IDs in the same order will produce the same result. This action requires admin permissions.Input Parameters
Output
Reorder Ticket Triggers
Reorder Ticket Triggers
ZENDESK_REORDER_TRIGGERSReorder Ticket Triggers. Updates the firing order of ticket triggers based on the provided trigger IDs. Use when you need to change the priority or execution order of ticket triggers in your Zendesk account. Important constraints: You must include EVERY ticket trigger ID in your account. Omitting any trigger ID returns 404 Forbidden. Additionally, reordering is not permitted if you have more than one ticket trigger category (returns LimitOneCategory error). This action is idempotent - re-running with the same trigger IDs in the same order will produce the same result.Input Parameters
Output
Reorder User Fields
Reorder User Fields
ZENDESK_REORDER_USER_FIELDSReorder User Fields. Updates the display order of custom user fields based on the provided field IDs. Use when you need to change the order of user fields displayed in user profiles or forms. This action requires admin-level access. This action is idempotent — re-running with the same field IDs in the same order will produce the same result.Input Parameters
Output
Request End User Verification
Request End User Verification
ZENDESK_REQUEST_END_USER_VERIFICATIONSend a verification email to an end user to verify ownership of their email address identity. The end user receives an email with a link to confirm their identity. Use when you need to verify an end user’s email address identity in Zendesk, such as when creating new end users or resolving identity verification issues. Note: This action can only be performed by verified end users.Input Parameters
Output
Request User Create
Request User Create
ZENDESK_REQUEST_USER_CREATESend a request to create a user in Zendesk. This sends the owner a reminder email to update their user profile information. Use when you want to prompt a user to complete their profile through the request flow rather than creating directly. This action is useful for onboarding flows where you want to collect user information through an email-based request rather than creating the user directly.Input Parameters
name field is mandatory. This action sends the owner a reminder email to complete their user profile.Output
Request User Verification
Request User Verification
ZENDESK_REQUEST_USER_VERIFICATIONSend a verification email to a user to verify ownership of their email address identity. The user receives an email with a link to confirm their identity. Use when you need to verify a user’s email address identity in Zendesk, such as when creating new users or resolving identity verification issues. Note: This action sends a verification email to the user’s identity address.Input Parameters
Output
Restore Multiple Deleted Tickets
Restore Multiple Deleted Tickets
ZENDESK_RESTORE_MANY_TICKETSRestore multiple deleted Zendesk tickets by ID. The returned counts and results reflect only results present in the immediate response; a job response without results yields empty counts and results.Input Parameters
Output
Restore Zendesk Ticket
Restore Zendesk Ticket
ZENDESK_RESTORE_ZENDESK_TICKETRestores a previously deleted ticket in Zendesk. Use when a ticket was accidentally deleted and needs to be recovered. The restored ticket will return to its previous state with all associated data intact. This action is reversible — tickets can be deleted again after restoration if needed.Input Parameters
Output
Search Custom Object Records
Search Custom Object Records
ZENDESK_SEARCH_CUSTOM_OBJECT_RECORDSSearch and filter custom object records in Zendesk using text queries and field filters. Returns paginated results with cursor-based navigation. Use when you need to find specific records within a custom object type, apply text searches or structured filters, and navigate through large result sets. This is a read-only operation. This action is useful for discovering records, running filtered queries on custom objects, and implementing paginated browsing through custom object data.Input Parameters
Output
Search Help Center Articles
Search Help Center Articles
Search Object Triggers
Search Object Triggers
ZENDESK_SEARCH_OBJECT_TRIGGERSSearch triggers for a specific Zendesk custom object by title, description, or active status, with sorting options.Input Parameters
Output
Search Zendesk
Search Zendesk
ZENDESK_SEARCH_ZENDESKTool to search for tickets, users, organizations, and groups in Zendesk using query syntax. Use when you need to find resources across Zendesk using flexible search criteria.Input Parameters
results. Zendesk’s search endpoint requires nested syntax: <result_type>(<resource1>,<resource2>). Combine multiple result types with commas. Common sideloads: users, groups, organizations. A flat comma list (e.g. ‘users,groups’) is silently ignored by Zendesk.Output
Search Organizations
Search Organizations
ZENDESK_SEARCH_ZENDESK_ORGANIZATIONSSearch organizations in Zendesk by external ID or name. Returns an array of organizations matching the provided criteria. Use when you need to find specific organizations by their identifier or name. An empty organizations array with count=0 means no matches found. Multiple organizations may share similar names — verify the correct organization via external_id or domain_names before proceeding with operations.Input Parameters
Output
Search Zendesk Users
Search Zendesk Users
ZENDESK_SEARCH_ZENDESK_USERSSearch for Zendesk users by query or external ID. Supports flexible user search criteria using Zendesk search syntax, including names, email, notes, and phone numbers.Input Parameters
query parameter supports the Zendesk search syntax for more advanced user searches. It can specify a partial or full value of any user property, including name, email address, notes, or phone. Example: query='jdoe'. See the Search API.external_id parameter does not support the search syntax. It only accepts exact ID values.Output
Set Default Custom Ticket Status
Set Default Custom Ticket Status
ZENDESK_SET_DEFAULT_CUSTOM_STATUSSets one or more custom ticket statuses as the default for their respective categories. Use this action when you need to specify which custom status should be the default (fallback) status for a given category (open, pending, solved, etc.). This operation is idempotent — running it multiple times with the same IDs will produce the same result. Allowed for: Admins only. Note: The IDs should be valid custom ticket status IDs that exist in your Zendesk account.Input Parameters
Output
Set Group Membership as Default
Set Group Membership as Default
ZENDESK_SET_GROUP_MEMBERSHIP_AS_DEFAULTSet a group membership as the default for a specific user in Zendesk. Use when you need to mark a user’s group membership as the default, meaning tickets assigned directly to the agent will assume this membership’s group. Requires both the user ID and the group membership ID. This action is useful for managing default routing preferences for agents in your Zendesk instance. Note that only one group membership can be the default at a time - setting a new default will automatically unset the previous default.Input Parameters
Output
Set Organization as Default for User
Set Organization as Default for User
ZENDESK_SET_USERS_ORGANIZATION_AS_DEFAULTSet an organization as the default for a user in Zendesk. Use when you need to change which organization is the primary/default for a user by specifying the organization ID directly. Only one organization can be the default at a time. This action is idempotent - setting the same organization as default multiple times will succeed without side effects.Input Parameters
Output
Show Access Rule
Show Access Rule
ZENDESK_SHOW_ACCESS_RULEShow a custom object access rule by its ID. Use when you have a custom_object_key and access_rule_id and need to retrieve the access rule’s details including its conditions, title, description, and timestamps. This is a read-only operation that does not modify any data. This action is useful for reviewing access control rules applied to custom objects in Zendesk.Input Parameters
Output
Show Custom Object
Show Custom Object
ZENDESK_SHOW_CUSTOM_OBJECTGet details of a specific Zendesk custom object by its key. Use when you have a custom object key and need to retrieve its metadata including name, description, attachment settings, visibility settings, and creation/update timestamps. This is a read-only, idempotent operation that returns the full custom object definition.Input Parameters
Output
Show Custom Object Record
Show Custom Object Record
ZENDESK_SHOW_CUSTOM_OBJECT_RECORDGet details of a specific Zendesk custom object record by its key and record ID. Use when you have a custom object key and record ID and need to retrieve the record’s metadata including name, custom fields, timestamps, and photo. This is a read-only, idempotent operation that returns the full custom object record definition. Photo is only available if allows_photos is enabled on the custom object.Input Parameters
Output
Show Many Job Statuses
Show Many Job Statuses
ZENDESK_SHOW_MANY_JOB_STATUSESShow many job statuses by their IDs in Zendesk. Use this action when you have multiple job status IDs from bulk operations (like ticket updates, user merges, or ticket merges) and need to check their status in a single request. Each ID in the comma-separated list will return its corresponding job status object if found. Endpoint: GET /api/v2/job_statuses/show_manyInput Parameters
Output
Show Many Tickets
Show Many Tickets
ZENDESK_SHOW_MANY_TICKETSShow multiple tickets by their IDs. Use when you need to retrieve specific tickets by their IDs to display ticket details, compare tickets, or bulk fetch ticket information. The ids parameter accepts a comma-separated list of ticket IDs (e.g., ‘35436,35437’). Returns tickets for valid IDs only; non-existent IDs result in an empty tickets array without error.Input Parameters
Output
Show Many Users
Show Many Users
ZENDESK_SHOW_MANY_USERSRetrieve multiple Zendesk users by their numeric IDs or external IDs. Use when you have a list of user IDs (from ticket payloads, search results, etc.) and need to fetch full user details for multiple users at once. Accepts up to 100 IDs per request. Provide either ids or external_ids, not both.Input Parameters
Output
Show Permission Policy
Show Permission Policy
ZENDESK_SHOW_PERMISSION_POLICYGet details of a specific permission policy for a Zendesk custom object by its ID. Use when you have a custom_object_key and permission policy ID and need to retrieve the policy’s details including the role name and record operation permissions (create, read, update, delete). This is a read-only, idempotent operation that does not modify any data. This action is useful for reviewing permission policies that control access to custom object records in Zendesk.Input Parameters
Output
Show Request
Show Request
Unassign User from Organization
Unassign User from Organization
Update Access Rule
Update Access Rule
ZENDESK_UPDATE_ACCESS_RULEUpdate an existing access rule for a custom object in Zendesk. Access rules control which records of a custom object users can access based on conditions. Use this action when you need to: - Change an access rule’s title or description - Modify the conditions that determine when the rule applies - Update access permissions for custom object records This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Zendesk App Installation
Update Zendesk App Installation
ZENDESK_UPDATE_APPS_INSTALLATIONUpdate an app installation in Zendesk. Use when you need to modify app installation settings such as enabling/disabling the app, restricting access by groups or roles, or updating app-specific settings.Input Parameters
Output
Update Automation
Update Automation
ZENDESK_UPDATE_AUTOMATIONUpdate an existing automation in Zendesk. Automations are business rules that automatically perform actions on tickets when certain conditions are met. Use this action when you need to: - Change an automation’s title, active status, or position - Modify the conditions that trigger the automation - Update the actions the automation performs - Deactivate an automation without deleting it This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Custom Object
Update Custom Object
ZENDESK_UPDATE_CUSTOM_OBJECTUpdate an existing custom object in Zendesk. Custom objects are user-defined data structures that allow you to store and manage custom data types. Use this action when you need to: - Change a custom object’s title, description, or pluralized title - Update visibility settings (include_in_list_view) - Enable or disable attachments and photos for the custom object This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Custom Object Record
Update Custom Object Record
ZENDESK_UPDATE_CUSTOM_OBJECT_RECORDUpdate an existing record for a custom object in Zendesk. Use when you need to modify an existing custom object record. This action updates fields on a custom object record. You can update the name, external_id, and custom_object_fields as needed.Input Parameters
Output
Update Custom Ticket Status
Update Custom Ticket Status
ZENDESK_UPDATE_CUSTOM_STATUSUpdate an existing custom ticket status in Zendesk. Custom ticket statuses allow you to define additional statuses beyond the standard statuses (new, open, pending, solved, closed) for your ticket workflow. Use this action when you need to: - Change the labels shown to agents or end users for a custom status - Update the descriptions explaining when to use the status - Activate or deactivate a custom status - Modify how a custom status appears in the ticket interface This action is idempotent — re-running with the same parameters will produce the same result. Requires admin permissions in Zendesk.Input Parameters
Output
Update Deletion Schedule
Update Deletion Schedule
ZENDESK_UPDATE_DELETION_SCHEDULEUpdate an existing deletion schedule in Zendesk. Deletion schedules define automated rules for deleting tickets, users, attachments, or other records based on specified conditions. Use this action when you need to: - Change a deletion schedule’s title, description, or active status - Modify the conditions that determine which records are deleted - Pause or reactivate a deletion schedule This action is idempotent — re-running with the same parameters will produce the same result. Note: The ‘object’ field cannot be modified after schedule creation.Input Parameters
Output
Update Dynamic Content Variant
Update Dynamic Content Variant
Update Many Dynamic Content Variants
Update Many Dynamic Content Variants
ZENDESK_UPDATE_DYNAMIC_CONTENT_ITEMS_VARIANTSSubmit a bulk update of variants for a Zendesk dynamic content item, specifying variant IDs or locale IDs and changes to content or status. The response contains a job status for tracking the operation.Input Parameters
Output
Update Macro
Update Macro
ZENDESK_UPDATE_MACROUpdate an existing Zendesk macro by ID. The title and actions are required and sent on every update; description, active status, and access restrictions can also be supplied.Input Parameters
Output
Update Many Automations
Update Many Automations
ZENDESK_UPDATE_MANY_AUTOMATIONSUpdate multiple automations in Zendesk in a single request. Use when you need to bulk update automation settings such as position, active status, or title for multiple automations at once. Note: You might be restricted from updating some default automations. If included in a bulk update, the unrestricted automations will be updated. This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Many Macros
Update Many Macros
ZENDESK_UPDATE_MANY_MACROSUpdate multiple macros in Zendesk in a single request. Use when you need to bulk update macro settings such as position or active status for multiple macros at once. This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Many Object Triggers
Update Many Object Triggers
ZENDESK_UPDATE_MANY_OBJECT_TRIGGERSUpdate the position or active status of multiple Zendesk custom object triggers in a single request.Input Parameters
Output
Update Many Zendesk Organizations
Update Many Zendesk Organizations
ZENDESK_UPDATE_MANY_ORGANIZATIONSBulk update multiple Zendesk organizations in a single request. Use when you need to update organization details such as name, notes, details, domain names, or tags for multiple organizations at once. The action is queued as a background job - use the job_status URL to poll for completion. Maximum 100 organizations per request. Note: Agents without permission restrictions can only update ‘notes’ on organizations.Input Parameters
Output
Update Many Tickets
Update Many Tickets
ZENDESK_UPDATE_MANY_TICKETSUpdate multiple tickets in Zendesk in a single request. Use when you need to bulk update ticket fields such as status, priority, tags, assignee, or group for multiple tickets at once. The API accepts up to 100 ticket objects per request. Changes are processed asynchronously and return a job_status object for tracking progress.Input Parameters
Output
Update Many Ticket Triggers
Update Many Ticket Triggers
ZENDESK_UPDATE_MANY_TRIGGERSUpdate multiple ticket triggers in Zendesk in a single request. Use when you need to bulk update trigger settings such as position, active status, or category for multiple triggers at once. This action allows you to update the order (position) or activate/deactivate multiple triggers efficiently. This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Many Users
Update Many Users
ZENDESK_UPDATE_MANY_USERSBulk update multiple Zendesk users in a single request. Use when you need to apply the same or different updates to up to 100 users at once. Provide either a single user object to apply identical changes to all specified users, or an array of users objects for individual updates per user. The operation is asynchronous and returns a job_status that you can poll to track completion. This action is idempotent — re-running with the same parameters will apply the same updates again.Input Parameters
Output
Update Many Views
Update Many Views
ZENDESK_UPDATE_MANY_VIEWSUpdate multiple views in Zendesk in a single request. Use when you need to bulk update view settings such as position, active status, or title for multiple views at once. Note: You might be restricted from updating some default views. If included in a bulk update, the unrestricted views will be updated. This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Object Trigger
Update Object Trigger
ZENDESK_UPDATE_OBJECT_TRIGGERUpdate an existing custom object trigger in Zendesk. Triggers define automated actions that execute when specific conditions are met on custom object records. Use this action when you need to: - Change a trigger’s title or description - Enable or disable a trigger - Modify the conditions that cause the trigger to fire - Update the actions the trigger performs This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Organization Field
Update Organization Field
ZENDESK_UPDATE_ORGANIZATION_FIELDUpdate a custom organization field in Zendesk. Use when you need to modify an existing organization field’s properties such as title, type, description, options, or other settings. All existing custom_field_options must be included on update — omitted options will be deleted. Returns the updated organization field object.Input Parameters
Output
Update Permission Policy
Update Permission Policy
ZENDESK_UPDATE_PERMISSION_POLICYUpdate a Zendesk custom object’s permission policy, including record access and exceptions. When any record operation is supplied, the request includes all four operations; omitted operations or omitted allowed settings are sent as allowed, with a null rule ID unless specified.Input Parameters
Output
Update Resource Collection
Update Resource Collection
ZENDESK_UPDATE_RESOURCE_COLLECTIONUpdate an existing resource collection in Zendesk. Resource collections are groups of related resources (like triggers, automations, or ticket fields) that can be managed together. Use this action when you need to: - Rename a resource collection - Modify the resources included in a collection - Update the configuration of an existing collection This action is idempotent - re-running with the same parameters will produce the same result.Input Parameters
Output
Update Side Conversation
Update Side Conversation
ZENDESK_UPDATE_SIDE_CONVERSATIONUpdate a side conversation on a ticket in Zendesk. Use this action to modify the state (open/closed) or subject of an existing side conversation attached to a ticket. Use when you need to: - Close a side conversation that has been resolved - Reopen a closed side conversation - Update the subject line of a side conversation This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Support Address
Update Support Address
ZENDESK_UPDATE_SUPPORT_ADDRESSUpdate an existing support address in Zendesk. Support addresses are email addresses that receive customer inquiries and can be configured per brand. Use this action when you need to: - Change the name of a support address - Set or change the default support address for the account - Associate a support address with a different brand Note: You cannot change the email address of an existing support address.Input Parameters
Output
Update Zendesk Target
Update Zendesk Target
ZENDESK_UPDATE_TARGETUpdate an existing target in Zendesk. Targets are endpoints that receive data when triggers fire (e.g., HTTP targets, email targets, webhook targets). Use this action when you need to: - Change a target’s title - Activate or deactivate a target - Update target-specific properties This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Ticket Field
Update Ticket Field
ZENDESK_UPDATE_TICKET_FIELDUpdate an existing ticket field in Zendesk. Ticket fields define the structure and properties of custom fields on tickets. Use this action when you need to: - Rename a ticket field or update its title - Update the description or agent-only description - Change the field’s position in the ticket form - Enable or disable a ticket field - Set visibility and editability for portal and agents - Make fields required for solving tickets or creating requests - Configure validation patterns for regexp fields - Set tags for checkbox fields This action is idempotent — re-running with the same parameters will produce the same result. Requires admin permissions.Input Parameters
Output
Update Ticket Trigger
Update Ticket Trigger
ZENDESK_UPDATE_TICKET_TRIGGERUpdate an existing ticket trigger in Zendesk. Triggers are business rules that automatically perform actions on tickets when certain conditions are met. Use this action when you need to: - Change a trigger’s title, active status, position, or description - Modify the conditions that trigger the action - Update the actions the trigger performs - Reassign a trigger to a different category - Deactivate a trigger without deleting it This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Trigger Category
Update Trigger Category
ZENDESK_UPDATE_TRIGGER_CATEGORYUpdate an existing trigger category in Zendesk. Trigger categories are used to organize ticket triggers in the Zendesk admin interface. Use this action when you need to: - Rename a trigger category - Change the display order of a trigger category - Update both name and position of a trigger category This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update User
Update User
Update Zendesk User Field
Update Zendesk User Field
ZENDESK_UPDATE_USER_FIELDUpdate an existing user field in Zendesk. Use when you need to modify the title, description, options, or other properties of a custom user field. Supports updating text, checkbox, dropdown, multiselect, date, integer, decimal, regexp validation, and lookup types. Only administrators can update user fields.Input Parameters
Output
Update Zendesk User Profile
Update Zendesk User Profile
ZENDESK_UPDATE_USER_PROFILEPartially updates a user profile in Zendesk by identifier. Use when you need to modify specific fields of an existing profile without replacing the entire profile. This action uses JSON merge patch semantics — only provided fields are updated. Use this action when you have an existing profile identifier and need to update specific profile attributes, identifiers, or the profile name. The identifier must follow the format source:type:identifier_type:identifier_value.Input Parameters
Output
Update Zendesk User Profile By ID
Update Zendesk User Profile By ID
ZENDESK_UPDATE_USER_PROFILE_BY_IDPartially updates a user profile in Zendesk by profile ID. Use when you need to modify specific fields of an existing profile without replacing the entire profile. This action uses JSON merge patch semantics — only provided fields are updated. Use this action when you have a profile ID and need to update specific profile attributes, identifiers, name, source, or type. This is different from UpdateUserProfile which uses identifier lookup instead.Input Parameters
Output
Update User Identity
Update User Identity
Update Current User Settings
Update Current User Settings
ZENDESK_UPDATE_USERS_ME_SETTINGSUpdate the settings for the currently authenticated Zendesk user. Use when modifying UI preferences like keyboard shortcuts, onboarding tooltips, theme preferences, or shared views order. This action modifies the caller’s own settings only.Input Parameters
Output
Update Users Profiles
Update Users Profiles
ZENDESK_UPDATE_USERS_PROFILESCreate or update a profile for a specified Zendesk user, identified by user ID and a profile lookup identifier. Supply the profile’s name and identifiers, with optional custom attributes, to establish or modify the user’s profile.Input Parameters
Output
Update View
Update View
Update Zendesk Account Settings
Update Zendesk Account Settings
ZENDESK_UPDATE_ZENDESK_ACCOUNT_SETTINGSUpdate Zendesk account-level settings including tickets, branding, localization, routing, and more. Use when you need to configure or modify account-wide settings that affect all agents and end users. Requires admin privileges to update most settings. Settings changes are persistent and affect all users.Input Parameters
Output
Update Zendesk Attachment
Update Zendesk Attachment
ZENDESK_UPDATE_ZENDESK_ATTACHMENTUpdates an attachment’s malware access override setting. Use when you need to enable or restrict agent access to attachments that have been flagged for malware.Input Parameters
Output
Update Custom Object Field
Update Custom Object Field
ZENDESK_UPDATE_ZENDESK_CUSTOM_OBJECT_FIELDUpdate an existing custom object field in Zendesk. Custom object fields define the structure and properties of data within a custom object. Use this action when you need to: - Rename a custom object field - Update the description or display properties - Change the field’s position in the UI - Enable or disable a field - Set validation patterns or make fields required This action is idempotent — re-running with the same parameters will produce the same result.Input Parameters
Output
Update Dynamic Content Item
Update Dynamic Content Item
ZENDESK_UPDATE_ZENDESK_DYNAMIC_CONTENT_ITEMUpdate a dynamic content item in Zendesk. The only attribute that can be changed is the name. Use when you need to rename an existing dynamic content item after confirming its ID. Note: Dynamic content items are used to store multilingual content for use in triggers, automations, and macros. Updating the name affects all references to this item.Input Parameters
Output
Update Zendesk Organization
Update Zendesk Organization
ZENDESK_UPDATE_ZENDESK_ORGANIZATIONUpdate an organization in Zendesk. After updating, re-fetch via ZENDESK_GET_ZENDESK_ORGANIZATION if downstream logic depends on current data.Input Parameters
name, notes, domain_names, external_id); invalid fields may be silently ignored. domain_names must be an array and is treated as a full replacement — always include existing domains alongside new ones to avoid removing them. Zendesk trims whitespace from name, so near-identical strings may collide on uniqueness validation.Output
Update Request
Update Request
ZENDESK_UPDATE_ZENDESK_REQUESTSUpdate a Zendesk ticket request by ID, including fields such as status, priority, assignment, tags, and custom fields, or add a comment.Input Parameters
Output
Update Zendesk Ticket
Update Zendesk Ticket
ZENDESK_UPDATE_ZENDESK_TICKETTool to update a ticket in Zendesk. Use when you need to modify ticket fields like status, priority, or subject after confirming the ticket ID.Input Parameters
Output
Upsert Custom Object Record By External ID or Name
Upsert Custom Object Record By External ID or Name
ZENDESK_UPSERT_CUSTOM_OBJECT_RECORD_BY_EXTERNAL_ID_OR_NAMECreate or update a Zendesk custom object record by external ID or name, with external ID taking precedence when both are supplied. If no name is supplied in the request or record data, the payload uses “Untitled Record” as the name.Input Parameters
Output
Verify Subdomain Availability
Verify Subdomain Availability
ZENDESK_VERIFY_SUBDOMAIN_AVAILABILITYVerify if a subdomain name is available for use in Zendesk. Returns a success boolean indicating whether the subdomain can be registered. Use when checking if a desired subdomain name is available before creating a new Zendesk account or subdomain.Input Parameters
Output
Verify Support Address
Verify Support Address
ZENDESK_VERIFY_SUPPORT_ADDRESSVerify a support address forwarding in Zendesk. This action sends a verification request for the specified support address to confirm that the address is properly configured and can receive email forwarding. Use this action when you need to: - Verify a newly created support address is working correctly - Re-verify an existing support address after configuration changes - Confirm email forwarding is properly set up for a support address This action is idempotent — verifying an already-verified address will return success.Input Parameters
Output
Verify User Identity
Verify User Identity
ZENDESK_VERIFY_USER_IDENTITYSet a user identity as verified in Zendesk. This action marks an email address or other identity as confirmed, indicating the user has proven ownership. Use when you need to manually verify a user’s identity after they have completed an out-of-band verification process or when you want to override the verification status for administrative purposes. Note: This action cannot verify the account owner’s email identity due to security restrictions.