Please select the list of resources you would like to include in this integration. You can choose specific resources or select "all" to include all team resources.

Pinghome is a monitoring & observability platform that gives teams peace of mind

Pinghome

You will need to create a **descending** by ID "view" in Zendesk with **no** grouping and select it here. [Click here to learn more!](https://zapier.com/apps/zendesk/help#how-to-create-a-zendesk-custom-view)

Select the tag(s) you wish to watch for changes. If you do not select a tag, the trigger will fire for any new tag added.

Choose the ticket to watch for activity (audits). Shows recent tickets. This field is required if you are not a Zendesk admin.

Write a search string to determine how we'll look up the agent in Zendesk. For more information, visit [the Zendesk docs](https://support.zendesk.com/hc/en-us/articles/203663226#topic_rvz_afv_uc).

Search by Ticket ID: This method retrieves the ticket directly and provides immediate, up-to-date information. 

 Search API Query: This method searches across all tickets but may not immediately reflect recent updates. There can be a delay of 10-30 seconds before new or modified tickets appear in search results.

Select the way you want to search for the ticket. This defaults to searching by API Query.

Write a search string to determine how we'll look up the group in Zendesk. For more information, visit [the Zendesk docs](https://support.zendesk.com/hc/en-us/articles/203663226#topic_wcx_ifv_uc).

ID of the ticket for which to retrieve the last comment.

Write a search string to determine how we'll look up the organization in Zendesk. For more information, visit [the Zendesk docs](https://support.zendesk.com/hc/en-us/articles/203663226#topic_gok_ffv_uc).

Write a search string to determine how we'll look up the ticket in Zendesk. For more information, visit [the Zendesk docs](https://support.zendesk.com/hc/en-us/articles/203663226#topic_crj_yev_uc).

Write a search string to determine how we'll look up the user in Zendesk. For more information, visit [the Zendesk docs](https://support.zendesk.com/hc/en-us/articles/203663226#topic_rvz_afv_uc).

Note: the assignee must be in the default group (or specific group selected below) else an error will occur.

You can add emails of non-Zendesk users here as Collaborators.

To set the Requester, you must specify the Requester Name in this field AND the Requestor Email in the next field.

To set the Requester, you must specify the Requester Email in this field AND the Requestor Name in the previous field.

If selected, this person will be set as the submitter of the ticket. Defaults to the Requester.

If selected, this will set the form to render for this ticket. _Note: this is only applicable for Zendesk enterprise accounts._

Note: Only for Zendesk customers on plans with multi-brand support. More info [here](https://www.zendesk.com/product/pricing/)

An id you can use to link Zendesk Support tickets to local records

A comma separated list of emails to add as CC. Note: Email CCs will not be updated if an internal comment is also added while creating the ticket

You can only attach files when a comment is added to a ticket.

*Must* be unique. Zendesk does not allow duplicate organizations with the same name.

In this field you can store any details about the organization. e.g. the address

In this field you can store any notes you have about the organization.

Comma-separated list of tags you want to apply to the new organization.

Comma-separated list of domain names to automatically associated with this organization (format: "zapier.com, google.com").

A unique external id, you can use this to associate organizations to an external record.

New tickets from users in this organization are automatically put in this group.

End users in this organization are able to see each others tickets.

End users in this organization are able to see each others comments on tickets.

*Must* be unique. Zendesk does not allow duplicate users with the same email address.

In this field you can store any notes you have about the user.

Phone number for this user (format: +1 (555) 123-4567).

Comma-separated list of tags you want to apply to the new user.

Can be one of the following: "end-user", "agent", or "admin". Defaults to "end-user" if set and not one of those values.

Specify if you know this user is who they say they are?

A list of tags to remove from the ticket. Select a tag from the list, or use a custom value.

Public comments are visible to the end-user. Setting no will create an internal note instead of a comment.

Defaults to "Plaintext/Markdown" if a new Comment is provided and this field is blank.

A list of tags to add to the ticket.Select a tag from the list, or use a custom value.

Choose which organization to update. Looked up by ID.

Options: "true" or "false". End users in this organization are able to see each others tickets.

Options: "true" or "false". End users in this organization are able to see each others comments on tickets.

Choose which ticket to update. Looked up by ID.

The new status. Options: "new", "open", "pending", "hold", "solved", "closed".

Options: "problem", "incident", "question", "task".

A comma separated list of tags. Note: This will overwrite the existing tags. To add or remove tags, use the "Additional Tags" or "Remove Tags" fields

A comma separated list of tags to add to the ticket. Note: This field will not overwritte existing tags 

A comma separated list of tags to remove from the ticket.

Choose which user to update. Looked up by ID.

Requests can only be made to domains associated by this application. View [documentation](https://help.zapier.com/hc/en-us/articles/12899607716493) for more details.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Zendesk is a web-based help desk support tool that makes it simple to provide great customer support.

Connect Zendesk to Zapier to streamline and organize your customer interactions so you can focus on providing the best customer experience. Use Zapier to automatically take care of manual work like adding tickets to your team's project management app or creating tickets from form entries.

Here are some creative ways to use Zendesk and Zapier:

 Pull all your customer input into Zendesk so your team can find all feedback in one place. Turn Gmail emails, Typeform entries, and Twitter mentions into Zendesk tickets on the fly.

 Keep your team in the loop. When there's a new commit on your GitHub or GitLab issues, update corresponding Zendesk tickets.

 Maintain a complete list of customers in Zendesk by piping new customers from Chargify into Zendesk new users.

Zendesk

Help Scout is the ideal small business help desk. You can deliver great email support and get setup in minutes, without any of the typical help desk complexities.

Help Scout

Freshdesk is an online helpdesk software with multiple channel customer service to support customers across email, phone, chat, web, Twitter and more.

Freshdesk

HappyFox is a customer support, ticket support software that ensures lowest response time for all your customers queries. A really simple help desk!

HappyFox

Set up this Zap to automatically update Zendesk tickets whenever the state of a resource changes. This integration keeps you responsive to updates effortlessly.

Pinghome + Zendesk

Update Zendesk tickets for new state changes in Pinghome

Supported triggers and actions

State Change

Resource ListRequired

About Pinghome

Related categories

About Zendesk

Related categories

Similar apps

Help Scout

Freshdesk

HappyFox

Related Zap Templates

Related Zap Templates