Feature Request: Triggers - Action: Add Internal Note as a trigger action

Hi we have various use cases for this 

I Put simply we want to outline the next steps for the agent to take in the comments section

I would have thought it would be straight forward to add this feature

Hey Corey, and other people looking for a way to add an internal note via. an http target, you can use the below in your JSON.

Remember the target should be using the PUT method, and that Zendesk does not support this way of updating your tickets because of race conditions, also mentioned previously in the comments for this post. 

{
  "ticket": {
    "recipient": "email@domain",
    "comment": { "body": "Add your internal note here", "public": false }
  }
}

#helpsome regards,
Simon Blouner
Zendesk Consultant @ helphouse.io

We have a couple of use cases for this:

1. Notify an agent when a field is set, for example something like 'this field was set and now you should do x'

2. As a workaround to the fact that Zendesk doesn't have multiple conditions on a ticket form. For example, I want to only have field 3 show up when field 1 has value a and field 2 has value b. That isn't possible in Zendesk, so as a workaround I want to show the field the whole time and let the agent know by adding an internal comment if they save the ticket and it isn't set. So yes.. I now need a workaround for the workaround! 

I would also love to be able to do this for a few reasons. 

1. I have an automation that looks for "On Hold" tickets that have not been updated in 48hrs and changes the status to "Open". The intent here is to force a review/followup from my team members with the appropriate party so we if any resolution has been made. I would like the automation to add a private note to the effect of "This ticket was automatically reopened due to..." so the agent can quickly identify the reason without having to click through to events and then need to understand how events work. I want to keep it as simple and inline as possible. 

2. I have a trigger that will change (via URL target) the Reply From address, so that I can force one support address per group. However, this interferes with the "Notify Requester of Received Request Trigger" sometimes along with other issues that have been brought up on the forums related to this. I would really like to be able to just assign a specific support address to each group natively so that, no matter what, replies send from a "Support" group come from support@, Technical Service from tech@, etc. regardless of what address the customer actually send to. 

3. Similarly to item 1, I have an trigger that looks for replies/updates to side conversations and reopens the ticket, again to force a review of it. (Because the system notifications are inadequate and really easy to miss). So I would be using this to add a private comment to the effect of "This ticket has been reopened because a side conversation has been updated".

Lastly, a lot of the comment here refer to a helpful instructional guide for using URL targets to do this, but the link (Link removed by the Zendesk Community Team. Post has been archived due to outdated information.) is no longer available and I would really like to see the instructions that have been seen by others as an effective workaround. 

To change the reply from address in #2 I have a HTTP JSON PUT target set up called "Update Zendesk Ticket".  On the trigger, I use the action Notify Target with a JSON Body of {"ticket": {"recipient": "email@domain"}}

What would the JSON Body code be to create a new private note? I imagine something to the effect of replacing "recipient with the correct attribute name.

David

Yes that should be fine. Hope it goes well.

Ok, that's quite clear.

However, seems like if it's causing problems then I can just deactivate the trigger/automation and then it will all revert to working fine, no?

David

Zendesk have not gone so far as to remove these articles. But please see here for the official view on these techniques.

Thanks Graeme for pointing that out!

I was under the impression that this was actually encouraged by Zendesk, being promoted into an article, albeit due to their inability to provide this feature built-in.

David

Under Settings>Extensions, it looks like you have selected an HTTP target. The article uses a URL target.

I should say that these techniques to update tickets can be very useful but are discouraged by Zendesk. They can create race conditions that may lead to problems.

Hope that helps,

Hi all,

I wonder if there's anyone here who could help me out. I was following the steps for workaround in this great article: 

https://support.zendesk.com/hc/en-us/community/posts/205384468-Create-automated-public-follow-up-for-tickets-in-a-Pending-state 

and when I went to define the target I didn't get the same options - it seems that this screen was updated:

Content Type wasn't mentioned in the article. He said to enter:

• "Attribute Name = ticket[comment][body]"

The article is, of course, closed for commenting. 

Can anyone help me?