Support Trigger recipe megathread! Help putting together and troubleshooting Support triggers - post your questions here! | Community
Skip to main content

Support Trigger recipe megathread! Help putting together and troubleshooting Support triggers - post your questions here!

  • May 30, 2019
  • 7 replies
  • 0 views
Nicole17

We're trying something new here in the Zendesk Community: rounding up all of your questions on a topic in one place, and then providing the answers right in your comment. 

For this first one, we're collecting questions about Support trigger recipes, i.e. how to set up a trigger to do a specific action, or troubleshooting a trigger that you have set up but isn't working correctly. 

When you ask your question, please be sure to include the following: 

  • What exactly you want the trigger to do 

  • A screenshot of the trigger (if it's an existing one that you want us to troubleshoot) 

  • Information about other related triggers, if it's relevant

Our team of trigger experts will work to get your questions answered, and some may even get turned into knowledge base articles. 

Users who know a few things about triggers are encouraged to help out and drop some knowledge here as well. See a question you can answer? Dive in! 


-----

Additional handy info about triggers: 

-----

Questions about Chat related triggers should be posted in the Chat Q&A topic. 

    7 replies

    Dan95
    • Dan95
    • June 6, 2019
    This is more a request for what I wish you could do with triggers - maybe someone has some ideas about how we could do this, with the current feature set?
     
    What would make triggers more powerful, and more efficient to manage, would be to add an option for more advanced conditions.
     
    For example, currently you can do something like this:
    IF <this> AND <this> AND <this> AND (<this> OR <this> OR <this>) THEN...
     
    We would love to be able to do this:
    IF <this> AND <this> AND (<this> OR <this>) AND (<this> OR <this> OR <this>) THEN...
     
    I'm sure one of the focuses for triggers is to keep them simple to use.
    I think adding an 'advanced conditions' button, that then allowed users to add multiple ANY conditions, a bit like this would work:
     
    I'm sure it's not a small change in the back end for Zendesk, but it would make consolidating, and managing our long list of Triggers much more efficient!
     
    Nicole17
    • Nicole17
    • Author
    • June 6, 2019

    Thanks for sharing your thoughts, Dan! Ideas and feature requests should be posted to the Support Product Feedback topic

    Dan95
    • Dan95
    • June 7, 2019

    Cool - I've already raised this as a feature request actually.  

    I just thought I'd post it here as well, in case anyone had any ideas about how to do something similar with the current feature set.

    L
    • Lee16
    • June 11, 2019

    Hi everyone!

    We use a custom ticket field to pull through phone numbers from our bespoke contact us page.

    I want to make a trigger that 'updates' the phone number for the user profile depending on whatever is in this field.

    Does anyone know how I can do that? I feel like it would need to use an extension target.. but any ideas would be really appreciated!

    Brett13
    • Brett13
    • Community Manager
    • June 11, 2019

    Hey Lee,

    Awesome question!

    This Trigger is a little more complex and will require you to create a Target as you mentioned. You could possibly use some Liquid Markup in your newly created Target to capture that phone data from the ticket that was just generated.

    To update the users profile after you've obtained the phone number, you'd need to make an API call directly to that user. 

    The Trigger itself would be used to notify the Target you've created using similar conditions as shown below:

    My knowledge with regards to the API and Liquid Markup is rather limited but hopefully the above is enough to get you started!

    M
    • Max35
    • June 20, 2019

    Hey @Dan, I agree with your assessment that complex log would be very helpful. We used a workaround to accomplish something similar, I believe, by creating a second set of triggers which applies a second tag, then used "contains at least one of" condition to specify the [AND (xxxxxxx OR zzzzzzz)] part of your statement above. 

     

    For example: 

    - Ticket > is > created

    - Group > is > Customer Support

    - Tags > contain at least one of > "brand_x" "brand_z"

    Brett13
    • Brett13
    • Community Manager
    • June 24, 2019

    Thanks for sharing Max!!

    Terms & ConditionsCookie settingsAccessibility statement