Reordering and sorting triggers

Return to top
Have more questions? Submit a request


  • Bora


    I have 2 triggers that are set to automate first responses, both are set to send when Status = New. I need the one Trigger to activate only if the 1st does not. I've repositioned them as directed here, but the 2nd trigger continues to send it's message before the 1st one does.  

    The first trigger is making an API call before making it's public comment, which may explain why the 2nd one is beating it to the punch. But I still only want the 2nd Trigger to activate if the 1st trigger sends nothing.

    I've added a tag to the 1st trigger and included a condition that tag =/= that tag in the 2nd trigger to prevent double messaging, but it's not working and the 2nd trigger continues to act first. Please help. 

    Thank you, 




  • Wenbo Zhu

    Having the similar issue as Bora. Please help.




  • Delores Cooper
    Zendesk Customer Success

    Hi there!

    At an initial glance, I suspect that your triggers are following the triggers cycle pictured below. It can be a bit confusing. In order to confirm though I'll create tickets for both of you in order to get more information on your individual use cases. Talk shortly!

  • Jihoon Lee

    I am currently using over 100 Trigger.

    Previously, I could see all my triggers using the "? Per_page = 300" parameter.

    And I was able to move any trigger in the list to any position I wanted.

    Recently, however, this parameter does not work after the recently trigger update.

    So currently I can only rearrange between triggers between 1st and 100th, and only between 201 and 300th triggers.

    I want to sort the 102nd trigger after the 80th trigger.

    For now, but it's impossible.

    How can I do what I want?

  • Jonathan March
    Community Moderator

    Hello, @이지훈 are you still experiencing this problem?

    I am not able to replicate it. We have over 200 triggers, and when I click on a trigger's menu  and choose "select position", it shows all available triggers (from 1 to 200+).

    If you are still experiencing this problem, it would be a bug, and should be reported to Zendesk Support.


Please sign in to leave a comment.

Powered by Zendesk