Zendesk

This action previews how a Zendesk macro would affect a ticket without actually applying the macro. It shows the ticket as it would appear after the macro is applied.

Autocomplete problems in Zendesk. Use when you need to find problem suggestions based on a partial search text for ticket categorization or troubleshooting.

Search for Zendesk users by name prefix using the POST /api/v2/users/autocomplete endpoint. Returns an array of users whose name starts with the provided query. Use when you need to find users by name prefix for quick user lookup and autocomplete functionality.

Check 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.

This action retrieves the count of deleted users within a Zendesk account. It provides a quick way to determine the total number of deleted users for reporting or operational needs.

This action retrieves the approximate count of tickets where a Zendesk user is listed in the CCD field. This is useful for tracking how many tickets a user is copied on, which can help with reporting or workload analysis.

This action retrieves the total count of records for a specific custom object type in Zendesk. It returns both the current count value and the timestamp of when the count was last calculated.

This action retrieves the approximate count of organizations within a Zendesk account. It returns both the current count value and the timestamp of when the count was last calculated.

Create an access rule for a custom object to control data access permissions.

Installs a Zendesk app with specified settings and optional restrictions.

Sends a notification to currently open instances of a Zendesk app, triggering a custom event with optional data payload. Use when you need to push real-time updates or alerts to agents using a specific Zendesk app.

Search for Zendesk tags using autocomplete via POST request body. Use when you need to find tag suggestions based on a partial tag name for tagging tickets or organizing content.

This action creates a new automation in Zendesk that automatically performs actions on tickets when specified conditions are met. Useful for automating ticket routing, priority changes, and notifications.

This action creates a bookmark for a specific Zendesk ticket, allowing you to save a quick reference to that ticket.

Redact sensitive content from a ticket comment in Zendesk using the Agent Workspace method. Use when you need to permanently remove or hide sensitive information such as personal data, credentials, or inappropriate content from ticket comments. This action is irreversible — redacted content cannot be recovered once removed. Note: Requires Agent Workspace to be enabled and (for Enterprise accounts) agents need a custom role with redaction permissions. Closed tickets cannot have comments redacted.

This action submits a bulk job to perform create, update, delete, or upsert operations on multiple records of a Zendesk custom object type. The job runs asynchronously and returns a job ID that can be used to track progress.

This action creates a new record within a specified custom object type in Zendesk. Custom object records allow you to store and manage structured data beyond standard Zendesk entities.

This action uploads a file and attaches it to an existing custom object record in Zendesk. You can attach various file types including documents, images, and other files.

Creates a new custom ticket status with agent and end user labels, status category, and description.

This action creates a new deletion schedule in Zendesk that automatically deletes records (tickets, users, attachments, etc.) when specified conditions are met. Useful for data retention policies and automatic cleanup of old records.

This action creates a new dynamic content item with support for multiple locale variants. Each variant contains localized text that will be displayed based on the end user's language setting.

This action creates a new locale variant for an existing dynamic content item. Each variant provides localized content for a specific locale.

Add 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.

This action creates a group membership in Zendesk, assigning an agent to a group. It requires a user ID and group ID and returns the created membership object.

This action bulk imports up to 100 tickets into Zendesk at once using the ticket import endpoint. It is ideal for migrating tickets from another system, setting up test data, or creating multiple tickets efficiently in a single API call.

This action creates multiple locale variants for an existing dynamic content item. Each variant provides localized content for a specific language.

Create 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.

Create 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.

This action creates a new trigger for a Zendesk custom object. Triggers automatically perform actions (like sending notifications or updating fields) when specified conditions are met on custom object records.

This action creates a new custom organization field in Zendesk. It supports various field types including text, dropdown, checkbox, date, decimal, integer, lookup, multiselect, regexp, and textarea.

This action creates a new organization membership in Zendesk, linking a user to an organization. This allows the user to access tickets and data associated with that organization.

This action bulk creates up to 100 organization memberships in Zendesk at once. Each membership links a user to an organization. Use when onboarding multiple users to organizations in one API call.

Merge two organizations in Zendesk, combining all users and tickets into the winner organization.

This action sets tags for a Zendesk organization. Tags are used to categorize organizations and make them easier to find and filter. This operation will replace any existing tags with the new set provided.

This action creates a subscription linking a specific user to a Zendesk organization, enabling the user to access organization resources and receive notifications.

Create or update multiple users in Zendesk in a single request. Use when you need to batch create or update up to 100 users at once. New users require a 'name' field; existing users are matched by 'id'. Returns a job_status with results for each operation. This action is idempotent — re-running with the same parameters will produce the same results.

This action creates a new organization in Zendesk if it doesn't exist, or updates an existing one if external_id matches. This is an idempotent operation useful for syncing organizations from external systems.

Create or update a Zendesk user. If a user with the same email or external_id exists, it updates that user. Otherwise, it creates a new user. Use when you need to upsert user records - idempotent based on email or external_id matching. Returns 200 for existing users, 201 for newly created users.

This action bulk unregisters specified mobile devices from receiving Zendesk push notifications. It permanently removes the device tokens and stops push notifications from being sent to those devices.

Creates a resource collection that batches multiple operations on Zendesk resources (such as updating tickets) into a single request. Returns a job status to track progress.

This action creates a private side conversation on a Zendesk ticket. Side conversations allow agents to communicate privately without the customer seeing the message. Recipients can be Zendesk users, Slack channels, support groups, or Microsoft Teams channels.

Create 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.

Export 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.

This action creates a content pin on a Zendesk ticket, allowing you to attach helpful resources like articles or external content for easy reference.

This action creates a new custom ticket field in Zendesk supporting text, textarea, checkbox, date, integer, decimal, regexp, partialcreditcard, multiselect, tagger, and lookup field types. Define validation rules, display options for agents and end users, and conditional requirements.

This action creates or updates a selectable option for a dropdown or multiselect ticket field in Zendesk. Provide the ticket field ID, option name, and option value. The option will be added to the dropdown list shown to agents and end users.

This action creates a new trigger in Zendesk that automatically performs actions on tickets when specified conditions are met. Useful for automating ticket routing, status changes, and notifications.

Creates a batch job to perform operations on ticket trigger categories in Zendesk. Use this to update multiple trigger categories in a single request.

Creates a new trigger category to organize business rules and automation workflows.

This action creates or updates a selectable option for a dropdown or multiselect user field in Zendesk. Provide the user field ID, option name, and option value. The option will be added to the dropdown list shown to agents and end users.

Add an identity (email, phone, social) to an existing Zendesk user.

Record an event against a Sunshine user profile

This action logs out multiple users from Zendesk by terminating their active sessions. It requires a comma-separated list of user IDs, is irreversible, and the users will need to re-authenticate.

This action creates a new organization membership for a specific user in Zendesk, linking that user to an organization. This allows the user to access tickets and data associated with that organization.

Set tags on a Zendesk user via POST request to /api/v2/users/{user_id}/tags. Use when you need to add or update tags on a specific user. Note that this replaces all existing tags on the user with the provided set of tags. This action is idempotent.

This action creates a new view in Zendesk. Views are saved filters that help organize and prioritize support tickets. You can define conditions, display columns, grouping, and access restrictions.

Preview a Zendesk view by defining conditions and execution settings to see which tickets match the criteria without saving the view.

This action previews how many tickets match a set of filter conditions for a Zendesk view. It helps verify view definitions before saving them by showing the exact count of tickets that would match.

This action uploads a file to Zendesk that can later be attached to tickets or ticket comments. The uploaded file returns a token and URL that you use when creating or updating tickets.

This action creates a new custom object type in Zendesk. Custom objects allow you to store and manage structured data beyond standard Zendesk entities.