Kevin

Thanks for the update Jay! 

Disregard my point 1. The ticket commenting works in the method you described. I just assumed you would be able to reach the target URL, and because I couldn't, thought it would not fire correctly. Not the case. Everything works great!

As for the authentication information, I currently have it working using my Zendesk login. Not sure if both methods are applicable, but everything is automating for me. 

Thanks again for this great tip!

As an update, adding 'Ticket Tags doesn't contain = solve_ticket' to the conditions corrected my #3 issue above.

Great stuff! This has been a thorn in my side for a long time. I'm having some challenges implementing though:

1. The URL target is not working when i visit it directly, but the test says 'message successfully sent'. When I visit the URL, I receive a message - {"error":"InvalidEndpoint","description":"Not found"}. When I remove everything after 'tickets', I do not get the error. 

2. For the authentication, the target test is only a success when I use my Zendesk login credentials, not the TOKEN. And it is only a success when I leave the full {{ticket.id}}.json?ticket[comment][public]=true on the target URL.

3. When following the steps for "Auto Solving Pending Ticket" I get this error:

Automation could not be updated as:

• Automation must not run multiple times per ticket: It must have a time based condition that is only true once (Hours since created is 24) or a action that nullified a condition ("Priority Is High" and an action setting it to "Priority Is Urgent").

When I add an action such as 'updating ticket status' via the Zendesk options, the error goes away.