Conditions reference

Have more questions? Submit a request

4 Comments

  • Vigo W
    Comment actions Permalink

    Hello, what is the best way to express the conditions for when a ticket is created/updated or deleted? 

    I've noticed there is a field "update_type" which has values: "Create" or "Change", so I think the following means when a ticket is updated or created? 

    {
    "any": [
    {"field": "update_type", "value": "Create"},
    {"field": "update_type", "value": "Change"}
    ]
    }

     

    Somewhere else I've also read there is a "status" field, as well as "Ticket Is", but not sure how those translate to conditions. Additionally, I'm not sure how "ticket is deleted" is expressed as a condition, or if it's supported at all.

    Appreciate any insight, thank you!

    1
  • Sushant Patade
    Comment actions Permalink

    Agree with comment Vigo, not getting any input as how webhook will be triggered for Delete operation

    0
  • Chris H
    Comment actions Permalink

    Hello Vigo,

    Unfortunately delete is not an event that can be used in a trigger or automation. The status field is covered in the Additional conditions for triggers, automations, and views section stating
    status "is", "new", "open", "pending", "hold", "solved", or "closed"
    "is_not",
    "less_than",
    "greater_than"
    The ticket is portion is used in the UI for the created and updated conditions which is covered by the portion you copied in that code block.

    Best,

    Chris H
    Technical Support Architect

    Zendesk offers free, on-demand training for all of our products. Set up your account and start learning today at training.zendesk.com

    0
  • Leo Weng
    Comment actions Permalink

    Hi there, this reference was very helpful, but I think you missed the field "role" for when you want to check if the current_user is agent or end user.

    I was only able to learn about it by using Zendesk API to look at my other triggers to learn the name of the field. Please update this documentation with the field "role" so future users can more easily find it.

    0

Please sign in to leave a comment.

Powered by Zendesk