- Sending an SMS text message when an urgent ticket has been unattended for more than 48 hours
- Sending a notification to an X Corp stream when a new urgent ticket is created
Setting up a target
| Target | Description |
|---|---|
| Basecamp |
Using the Basecamp target, you can push ticket updates to a project as:
You need to enable API access in your Basecamp account to use this target. For information about setting up Basecamp, seeSetting up and using the Basecamp target. |
| Campfire | Send notifications to a Campfire chat room. |
| Clickatell | Use this target to send SMS messages using your Clickatell account. Follow the steps in Clickatell HTTP API Guide to setup the account, add a HTTP connection and obtain an API ID. |
| Send emails to a specific address. You can define the action in a trigger or automation. If the target email address is an external Support address on another Support account with whom you have ticket sharing agreements, the email notification is rejected by the target email address. A ticket will not be created. This happens in order to avoid an email loop. If you need to share support requests with another Support account, use theticket sharing featureinstead. Also, to prevent an email loop, you can't notify your own account's support addresses. |
|
| Get Satisfaction | Post public comments to Get Satisfaction topics for tickets created using the Zendesk moderator tool in Get Satisfaction. By creating this target, the necessary triggers and views and also add a useful widget in the home and ticket pages (you can remove those widgets if you don't need them) will automatically be created. |
| Pivotal Tracker | Create stories in Pivotal Tracker from a Zendesk Support ticket to easily prioritize support issues in your project backlog. The Pivotal Tracker target sends the Zendesk Support ticket ID to Pivotal Tracker when creating a new story. If you have enabled Pivotal Tracker's native Zendesk integration in the target Tracker project, a link back to the Zendesk Support ticket is created in the new story. |
| Twilio | Use this target to send SMS messages to a mobile phone using your Twilio account. |
| X Corp | Send notifications to an X Corp stream.
Note:Make sure that you protect your X Corp stream if you don't want notifications to be readable by the general public.
|
| URL | Pass URL parameters to any URL. You can use placeholders as values. Example: www.some-address.com?customer_name={{ticket.requester.name}}. Set up a script on your server to receive the request, and then you can do just about anything from there. To troubleshoot problems with the target, seeGet information about URL targets that aren't working.
Note:We don't recommend using URL targets to update tickets in Zendesk Support, which can result in multiple issues. Use for external targets only.
|
| Yammer | Send notifications to a Yammer stream. Follow the steps in this Yammer Target Guide to create a client application in Yammer and authorize this target to use the Yammer API. For more information, seeNotifying your Yammer feed. |
- InAdmin Center, click
Apps and integrationsin the sidebar, then selectTargets > Targets. - Selectadd target.
- All of the target options are listed. Select the type of target and enter the required target information (which varies from target to target).
- SelectCreate targetfrom the drop-down list at the bottom of the page. If you want to test the target before adding it, selectTest target.
- ClickSubmit.
Once you've set up targets, you can edit, delete, and deactivate and reactivate them. SeeManaging external targets.
Using targets in automations and triggers
Once you've set up targets, you can use them in automations and triggers. Here's an example of a trigger that notifies an X Corp account when an urgent ticket is created:
Since you're interacting with external targets, there may be a delay between when a trigger or automation runs and when you'll see the results in the external target (in the example above, that would be your X Corp home page or stream).
You can enter up to 8192 characters in theMessagefield of aNotify targetaction.
Avoiding timeout errors
If a timeout error is received within 10 seconds of a request being made, Zendesk retries the request. After 21 consecutive failed attempts to retry the request, Zendesk deactivates the target. You'll need to reactivate the target before you can use it again.
Zendesk admins receive a notification when a target is automatically deactivated. They don't receive a notification when a target is manually deleted or deactivated.
- The message body in the trigger or target page is blank.
- There's a problem with the receiving server.
8 Comments
Hello can you (zendesk) that payloads sent via the HTTP target is encrypted (HTTPS) or not encrypted (docs do not mention https so assumed plan text).
@...
As long as your target url is specified using https:// the HTTP target will use https:// & encrypt. While http:// will work we don't recommend using it except for maybe testing placeholder content (lorem ipsum, etc) to make sure your payload looks okay. In any production scenerio https:// should be used. I hope that helps, I'll file a ticket with the docs team to add some more context to the documentation.
Cheers!
Hello,
Can you notify a distribution list by adding it as an email target?
Yes, I have tested it on my end and it went through without any issue.
Is it possible to have these notifications get triggered to a chat within Microsoft Teams?
Instead of targets, you can utilize web-hooks instead. Microsoft teams have their own incoming web-hook that you can be used in Zendesk to send notifications. Unfortunately, we can't support you on how to set it up.
I've been trying to use a Target to send ticket data to Zapier. Everything seems to be working okay because when I test the webhook trigger in Zapier, the data is coming through. However, in Zendesk, when I check the Targets page, it shows 0 successful sends. It also doesn't show any errors on the Target Failures page for that target.
我问这个是因为Zapier不能parse the data I'm sending, so I'm wondering if there is a formatting error. Is there a way for me to check the data being sent to the target? The fact that it says "0 successful sends" makes me wonder if I'm doing something wrong.
The target is a POST method, and the trigger I have is sending the following message:
{"name": "{{ticket.requester.name}}",
"email": "{{ticket.requester.email}}",
"code": "{{ticket.ticket_field_32449767}}",
"title": "{{ticket.title}}",
"district": "{{ticket.ticket_field_23788466}}",
"message": "{{ticket.latest_public_comment_html}}"
}
将接收webhook看到JSON数据?
Thanks for any insight.
Steve
HiSunburst Support
Thanks for bringing this to our attention. To better assist you with your concern, I have created a ticket on your behalf. One of our Advocates will reach out to you to troubleshoot this issue further.
Have a great day! Thanks!
Pleasesign into leave a comment.