Using Triggers to automate your Helpdesk


Helpy triggers give you a powerful tool for customizing and automating the way your Helpy works.  Triggers are specific instructions that are followed when certain conditions occur in your Helpy.  They are listed using the event-condition followed by the actions(s) to be carried out:

Screen Shot 2017-03-15 at 10.12.55 AM.png 26.87 KB

Using triggers, you can automatically route new tickets to specific groups depending on the content of the ticket, auto-assign tickets to the next available agent, or send a JSON webhook when a high priority customer has a problem, or... well the possibilities are really endless.

Creating a Trigger

Triggers follow a pattern to identify when, where and what to do.  The ‘when’ is an event that has taken place in Helpy, the ‘where’ is a series of conditions that let you choose specific kinds of tickets to act on, and the “what” are actions that can be done to the matching ticket.

For example:

When a new ticket arrives, where the sender is, then assign it to the VIP Group.
When (Event) Where (Conditions) What (Action)

Choosing an Event

When designing a trigger, it is best to think about the event that will cause the trigger to fire.  Events range from “New ticket created” to “Ticket Closed”.  Here is a list of available events with a brief description of each:

  • A new ticket is created
  • A ticket is reopened
  • A ticket is marked pending- in other words it is waiting for a response from an agent
  • A ticket is moved to the trash
  • A ticket is moved to the spam folder
  • A ticket is marked "resolved"
  • A ticket is assigned to an agent
  • A ticket is assigned to a group
  • An agent replies to a ticket
  • An agent writes an internal note on a ticket
  • A user replies to a ticket

Focusing your Event with Conditions

Sometimes you may want to create a trigger that only occurs for “certain” tickets.  Say those written by your most important client.  You can ensure this happens by setting up a condition for your event- instructing it to occur only when the event and some other conditions are true.

Each condition is made up of 3 parts: the property, an operator and the value.  The condition from the example above is "where the sender is".  To set this up would look like this:

property: from email
operator: equals

You can build conditions using the following available properties and operators:

  • Ticket Subject
  • Ticket Body
  • Channel
  • Ticket Status
  • User Email
  • User Name
  • User Priority
  • Reply Body

And Operators

  • Equal to
  • Not Equal to
  • Contains
  • Does not Contain

The Action

The final part of a trigger is the “action”, or what will be done when a ticket event matches the conditions defined previously.  Available actions include:

Agent Assignment:
  • Assign to a specific agent
  • Assign to the next agent
  • Assign to the least busy agent
  • Unassign agent

  • Add an internal note
  • Reply to the topic
  • Assign to a group
  • Alert the ticket
  • Mark it as resolved
  • Send a JSON webhook - See separate article on using the external JSON API
  • Post a notification to Slack - See separate reference on integrating with Slack


Chirag Chhiat

How do I access triggers? I downloaded the latest version of Helpy but cannot access triggers anywhere. Is this only for the paid version of Helpy?

      Scott Miller

      This feature is only in the hosted version of Helpy.

          John Kloian

          Are there any plans to bring this feature to the open-source version?

              Scott Miller

              Not at this point.  This behavior is fairly easy to implement in the code with simple active record callbacks.

                  Did this solve your problem?