Max McDaniel

Thanks @..., was able to confirm that it doesn't appear to be an auth issue, as changing the credentials caused a different error. I'm not familiar with JSON/Liquid so not sure what would be a basic request to run, but when I left the JSON input blank it errored out with "400 Bad Request" ("both ticket IDs and arguments required"). 

I created a trigger to send the liquid script via email and it (I think correctly) delivered this for a ticket which did not have an attachment: 

What I don't know is how that translates into adding a tag to the ticket. 

Thanks @..., I tried copy/pasting the example you shared but received the same error. 

Is there something in the actual JSON that I need to be changing/adding? 

Based on the error, I don't suspect this is an authentication issue, but could that be the case?

Ash, in testing, I'm unable to get the trigger, which is firing successfully, to hit the extension I built. 

When I test the extension, I get an error:

{"error":"Unprocessable Entity","message":"Server could not parse JSON"}

Any thoughts?

+1 from me!