Trigger conditions and actions reference

Have more questions? Submit a request

49 Comments

  • Kevin
    Comment actions Permalink

    Hi Chris

    Thanks for the answer. The reason it does not make sense to me is - using the example you gave - wouldn't someone not being able to login to their account be a "problem?" I was under the impression that everything is a problem and if there is more than one occurrence then you make additional occurrences incidents

    0
  • Brett - Community Manager
    Comment actions Permalink

    Hey Kevin,

    I can definitely see how it could work in both cases. There's more of an explanation on the relationship between Problem and Incident tickets here: Working with problem and incident tickets

    0
  • Kevin
    Comment actions Permalink

    Hey Chris

    Without being too much of a pain, can you tell me why incident is defined in the way quoted in this article, and other Zendesk articles, if the intended use-case is that incident can either be attached to a problem or be stand-alone? Honestly, I think I wouldn't have had any of this confusion unless I read that. The same definitions of ticket type are also in "Creating Views To Manage Ticket Workflow"

    I'd like to suggest that the definition quoted here is changed.

    "Incident is used to indicate that there is more than one occurrence of the same problem. When this occurs, one ticket is set to Problem and the other tickets that are reporting the same problem are set to Incident and linked to the problem ticket."
    And
    "Problem is a support issue that needs to be resolved."

    0
  • Brett - Community Manager
    Comment actions Permalink

    Hey Kevin,

    Thanks for the clarification! I agree that this could be worded better in our documentation. I've flagged the article for the appropriate team to look at :)

    Thanks again for bringing this to our attention!

    0
  • Kevin
    Comment actions Permalink

    Fair enough, thank you Brett. 

    (also unsure why I was calling you Chris. My apologies)

    0
  • Brett - Community Manager
    Comment actions Permalink

    No problem at all Kevin!

    0
  • Jesse Rubenfeld
    Comment actions Permalink

    Why can't triggers use wildcards in tags like search can?

    0
  • Ethan
    Comment actions Permalink

    Hi Guys

    I'm wondering is there any way that for the custom field, all the conditions available for default fields in trigger to be added somehow!?

    To be specific, for example if you want to use "Status" in a trigger you have many options to select from the dropdown list as below:

     

    But if you have a custom field, only few items are available! Without having all those conditions, the custom fields won't help as much as they could if they had more conditions to select from. 

     

    1
  • Brett - Community Manager
    Comment actions Permalink

    Hey Ethan,

    Thanks for taking the time to share this with us! I'll be sure to pass this feedback along to the appropriate team so they're aware of this need.

    Cheers!

    2
  • David Waugh
    Comment actions Permalink

    Question regarding triggers - Is there there a way to only have the first trigger get processed and not the remainder of the triggers? 

    For instance, I have an RMM alerting system that sends emails to the Help Desk.  There is a trigger setup to automatically reply to the originator.  Unfortunately, the from address on the RMM does not accepts emails, so and NDR is received every time.  Is there a away to exclude a particular address when a trigger is processed so that the NDR is not received?

    Thank you

    David

    0
  • Brett - Community Manager
    Comment actions Permalink

    Hey David,

    Just to confirm, are you trying to prevent the trigger from firing when the requester of the ticket is a specific user (RMM)? If so, you could just tag that user profile which will carry over to the ticket.

    You can then set up your triggers to exclude any tickets that have the tagged set in the users profile.

    Let me know if the above doesn't make sense!

    0
  • David Waugh
    Comment actions Permalink

    Yes, that is exactly what I need to accomplish.  How would I tag that user profile?

    For instance, the from address is not a user already setup in Zendesk.  IT is coming from an external email address.

    Thanks

    David

     

    0
  • Brett - Community Manager
    Comment actions Permalink

    Hey David,

    This article will walk you through those steps :) Automatically tagging tickets from specific users and organizations

    I hope this helps!

    0
  • Naomi Watnick
    Comment actions Permalink

    Hi Friends - is there a way to trigger based on if the ticket was submitted/updated with an attachment attached?  And also attachment name and/or extension?  

    0
  • Ben Van Iten
    Comment actions Permalink

    Hi Naomi,

    That particular condition is not currently available with triggers. However if customers were to select a custom field (perhaps a checkbox) if they intended to attach a file you could run a trigger based off of that.

    I hope that is helpful!

    0
  • Naomi Watnick
    Comment actions Permalink

    hi Devan - Will tomorrow's AMA be in Zoom format?  How do we keep up to date with the questions being asked?

    0
  • Nicole - Community Manager
    Comment actions Permalink

    Hi Naiomi, 

    I am so sorry we didn't respond to this prior to the AMA. Our AMAs are Reddit-style, meaning that they happen in the community forum in a written format (as opposed to on Zoom or other video format.) 

    You can simply visit the AMA topic to see each of the questions asked and the answers provided. Here's where you can see all of our past AMAs

    0
  • pstrauss
    Comment actions Permalink

    If I create a trigger that's based solely on a USER(Requester) level custom field, when will the trigger execute? Does the agent need to save any one of the user's tickets before the trigger will execute, or is there a way to have it execute when the user field is updated (which is what we'd prefer in this particular use case).

    0
  • Ben Van Iten
    Comment actions Permalink

    Hi pstrauss,

    If there is a tag related to a user field, it won't push through to the ticket when that user field is updated. This field will cross over to the ticket when a new ticket is created, and the user field is already set. I hope that part makes sense.

    If you were able to update the tickets in bulk with the same tag that is present with the user field (if it is a field that has a tag related to it) and have the trigger fire based off of the tag instead of the user field, you could have both use cases accounted for. I know that isn't exactly what you were looking for, but depending on the use case it could work out for you.

    I hope this is helpful - please let us know if we can assist further!

    0

Please sign in to leave a comment.

Powered by Zendesk