Create a private comment automatically

Hey Kev! 

I've followed your instructions but the client call is failing- not super familiar with setting up an extension, do you have any tips on how to make sure it works?

Cheers!

Hey Ayryn,

Looks like there haven't been any updates on this post regarding your question.

Have you navigated to Admin>Channels>API>Target Failures to confirm the failure type you're running into?

You'll also want to be careful when using triggers to provide updates on tickets as there can be some odd behavior. I'd recommend taking a look at the following article for more information: Can I use a trigger and a target to update tickets?

Hope this points you in the right direction!

Thanks Kev!

This is exactly what i needed to do.  I will still need to test it but it is pretty straight forward.

Thanks again,

Yami  :=]

Hi Kev,

I tested and i am getting HTTP Errors; can it be because i did not place a User/Password?  If so, what would this be, my sign on ID and Password?

Thanks,

Yami

Hey Yamile,

Credentials shouldn't be required here but you can try adding them to see if that resolves the issue. Username would be the email address you use to log into your Support account and the password would be the same as your login password.

Hope this helps!

Hi Kev,

Thanks for the confirmation, 

I am still having the same error 401

"error": "Couldn't authenticate you"

I am not sure where to go from here?

{
  "error": "Couldn't authenticate you"
}

I’ll take a quick look at my settings in the office tomorrow and hopefully get back with a solution :-)

Thanks Kev! 

You may need to check your API Admin page to ensure you have password access enabled.  

You might also consider using a token instead of an agent password. If you use a token your user name would be email@domain.com/token (replacing the email address with your address of course). Your password would be your API token. 

Hi All

Need help, we have the same use case, where we want to add "private" note if certain conditions are met.

Has anybody experienced any issues with this method since Zendesk does not support this method due to race condition (Link below).

If yes, what kind of impact we are looking at?

https://support.zendesk.com/hc/en-us/articles/234658247-Can-I-use-a-trigger-and-a-target-to-update-tickets-

Hello

Does any one succesfully use this method ?

I have the same issu, Error during transmission: HTTP client call failed

I try with token, no token (my account), no accourt, always the same error

In API Admin page to ensure you have password access enabled has been check, OK

Any idea or clue ?

Thank you,

Best regard

Hi @Jean-Edouard Leblond -- I suggest submitting a ticket, so your specific account can be examined more closely. 

Know that this particular workflow is not officially supported. See Can I use a trigger and a target to update tickets? for more details.

I am trying to test the PUT command in Postman and a command terminal, when I run the URL with text after "false+", nothing is added to the ticket.

Is there a way different call I should be making to test this manually?

https://domainname.zendesk.com/api/v2/tickets/{{ticket.id}}.json?ticket[comment][public]=false+test comment

I know the approach in the original post has seemed to have worked in the past (passing field names and field values as query parameters) but it's not a supported or documented approach to updating a ticket. The official way of updating a ticket is to use the PUT /api/v2/tickets/{id}.json API.

Revamping the above instructions to use the documented API call, you would:

1. Create an "HTTP" target extension (not a "URL" target) using PUT method and Content Type of JSON.

2. Give the target extension a URL value of: https://your_subdomain.zendesk.com/api/v2/tickets/{{ticket.id}}

3.Enable Basic authentication and enter an agent level email and password. If you are using an "API token", the format for the email should be john@example.com/token with the password being the API token. See reference documentation for details.

4. Then, similar to the above, create a Trigger that fires on ticket creation. Have a "Notify target" action that calls the above HTTP target extension created in steps 1 thru 3

5. For the body of the trigger action's request you pass a JSON payload, similar to what's documented at PUT /api/v2/tickets/{id}.json

The trigger action's JSON for the above example would look like:

{
  "ticket":{
     "comment": {
                 "html_body": "CUSTOMER HAS RECEIVED 24 HOUR NOTIFICATION EMAIL.\r\n\r\n<hr>\r\n\r\n<p>Hi {{ticket.requester.first_name}}</p>\r\n\r\n<p>We just wanted to see if you have had time to take a look at our recent email? We haven't heard back from you and wanted to make sure we hadn't missed you.</p>\r\n\r\n<p>If you want to get in touch with any questions or comments you may have when you get a moment, or if you want to let us know if you need a little more time to digest the information, just hit reply. </p>\r\n\r\n<blockquote>{{ticket.latest_public_comment_formatted}}</blockquote>", 
                 "public"   : false
                }
  }
}

Note: If you're passing HTML in the JSON body, you need to set the "html_body" attribute and pass a valid JSON string.

Another note is that, technically, calling into your Zendesk instance from a target extension is not officially supported. It can work, but there are possible issues depending on the action, what other triggers are doing, and the expectation of the agent on seeing those background changes surface in the UI.

All that said, the above steps should accomplish the same action as the original post. Try that instead @Pete and let us know how it works!

Thanks Bryan followed this to a T and still cannot authenticate. So weird. Could this be related to Google SSO being the only method at which agents can sign in?

Ah, yes 24054238927 -- that's no doubt it. I didn't think of that. Because the trigger method only allows for "Basic" (i.e. Zendesk username/password credentials), not having that turned on would explain 401/unable to authenticate errors. Thanks for pointing that out!

If you need to use basic authentication (as in this case), you need to have password access enabled:

Having some other auth mechanism turned on (and Zendesk auth turned off) I could see also creating this issue:

Definitely check these things.

Thanks 6482129967. So I now have settings as shown in my two screenshots. I can successfully log in to my Zendesk as an admin without going through my SSO service. But when I use that same username and password for the basic authentication for the HTTP target, I still get the "cannot authenticate you" error. I have submitted a ticket to Zendesk early last week but have not heard back at all.

For whatever reason I can authenticate with POST but not with PUT. However, POST does not work in that while it authenticates, it returns and invalid end point and therefore the comment does not post.

Just closing the loop to confirm that I was able to get this to work. Austin with Zendesk Support helped me make sure I had this set-up correctly. So it does work!

This solved a huge headache for my team!

Thank you so much!

Seems like this would be so much easier if Zendesk just added 'set private comment' as an action choice for a trigger. Seems like a lot of hoops to go through for a simple task.

You aint wrong jack :-)

Although once the initial URL target is set up the "notify target" command is effectively acts the same as a "set private comment" option would. You don't need to create the target link everytime you want to create a new private comment trigger. so not a massive faff.

When I try this I'm getting a target error:

HTTP/1.1 401 Unauthorized

I've entered my username and password into the URL Target.

Anything else I need to do?

@Kev Walsh any ideas?