Tiggers/Automation-based Notifications: Workaround for posting comment in ticket

14 댓글

  • 공식 댓글
    Devan - Community Manager
    Zendesk Community Manager

    This is an amazing tip! I'll be sure to share this with others in our next Weekly Digest!

  • Andrew J
    Community Moderator

    Would it not be better to keep this all on the same ticket?  You should be able to use a http target to add a private note of the notification sent.  Would that help?

    0
  • Montana Steele

    @... - I agree that it's ideal to keep it all on the same ticket, and this is a workaround for that specific limitation, choosing to instead give agents context and creating a new follow-up thread (associated with the original ticket) that contains the notification that was sent. I am not very familiar myself with using http targets and do not know if that would create a similar workaround while keeping it on the same ticket! If you try that, please report back! 

    0
  • Andrew J
    Community Moderator

    Actually - it's easier with a URL target.  

    Admin (gear) > Extensions > Add Target > URL Target. Then use details as in image - substituting your URL and login.

    Full URL is https://yourURL.zendesk.com/api/v2/tickets/{{ticket.id}}.json?ticket[comment][public]=false

    Once done, just add an action to your automation (whatever is doing the message that you are needing to see).

    > Notify target , [your target as above], and the message you want your agents to see. something like 'Automatic message sent to user: "This is the message content" '

    You should no longer need to close the ticket to see the notification that was sent.

    0
  • Phil Williams
    Community Moderator

    ^^ That's the method we use. Works a treat :)

    0
  • Support Department

    This sounds way better than closing a ticket. 

    However, I'm not getting it work. What do I have to set as attribute to get a Private (internal) comment?

     

    0
  • Phil Williams
    Community Moderator

    If you set the URL as https://yourdomain.zendesk.com/api/v2/tickets/{{ticket.id}}.json?ticket[comment][public]=false+ and the Attribute Name as ticket[comment][body] Then this will setup the extension correctly.

    Within the trigger, you would then create a Notify Target action pointing at your new extension and enter the message you wish to add.

    This will then add the message as a private comment.

    0
  • Support Department

    It's working! Thanks a lot!

    0
  • Phil Williams
    Community Moderator

    Excellent, not a problem! :)

    0
  • Michael Huber

    Hi Phil,

     

    I tried your solution using the URL target to update tickets in the Dev System and that's exactly the solution I've been searching for. Did you ever had problems with this solution concerning a race condition or something else?

     

    Many thanks in advance and regards

    Michael

    0
  • Matt Taylor

    @... sorry for reviving a dead post, but does this still work for you? I'm unable to get anything published to the ticket within the Zendesk Sandbox

    0
  • Phil Williams
    Community Moderator

    Yep we use it every day. The key issue most people face is the race condition so you do need to be especially careful about that. If the desk encounters a race condition where the comments are continuously added then the API is disabled.

    I've never tested this in a sandbox environment so that could be the reason it's not working for you but we use this daily in our production environment.

     

    0
  • Kulin Joshi

    All of sudden this target stopped working and gives error: 

     

     

    Any idea?

    0
  • Austin Killey
    Zendesk Customer Care

    Hey there Kulin Joshi,

    Thanks so much for the heads up with that target error.  We'll have a good number of possibilities for what might be causing that: I'll open up a ticket on your behalf and we can tackle some troubleshooting together.  Catch up with you soon!

    0

댓글을 남기려면 로그인하세요.

Zendesk 제공