Using Warning and Violation Post Hooks

Performset provides an option to configure alternative conditional notifications to a specified list of agents or groups belonging to your Zendesk account and the use of this feature is described in an alternative article (Configuring Warning and Violation Notifications).

However, there might also be a need to perform other actions if and when a warning timer fires or violation occurs, such as the escalation and reassignment of the ticket to another group, or the sending of a notification to a recipient that isn't and agent in your Zendesk.

These actions must be achieved through the introduction of your own Zendesk triggers, but your Performset setup must be configured to generate a ticket update for use in the trigger conditions when a warning or violation occurs.

Configuring your Setup to Use Warning and Violation Post Hooks

If your setup hasn't already been configured to make use of warning and violation post hooks it will be necessary to submit a request to the CloudSET support team to make the necessary arrangements (support@cloudset.zendesk.com).

Once your setup has been configured, it will be possible to make use of the post hooks in your Zendesk triggers as described in the sections below.

Using the Warning and Violation Post Hooks in your Zendesk Triggers

The post hooks are intended for use within your Zendesk Triggers to identify when a warning or violation has occurred for an event, so the necessary action can be taken to avoid an impending breach, or escalate once a breach has occurred.

Post Hook Ticket Fields

For each event that has been configured to use 'Post Hooks', a ticket 'MarkPost' ticket field is generated in your Zendesk account.

Post Hook Option Values

Each of these 'MarkPost' fields includes an option value that is set by the Performset service if and when the warning timer fires for the associated event, or if and when a violation has occurred for the event.

Post Hook Triggers

The value of the MarkPost' field can be used in a trigger condition to identify when a warning or violation has occurred for an event.

This allows for standard Zendesk actions to be taken, for example, using the Zendesk Email Target extension to send a message to an external email address.

See the following Zendesk article for full details on the use of external targets: Notifying external targets

**NOTE** It is important to reset the value of the 'MarkPost' ticket field to avoid the trigger firing again each time the ticket is updated.