Event Actions allow users to create actions based on their Event views for their process management.

Event Actions

The real power of events comes from the ability to create actions based on specific views. This enables you to tie events that UpGuard detects into your own processes.

Event Views

To create an event action you must first choose or create an event view. For more information on how to create an event view, please refer to Events.


Before turning on an action, it is critical that the impact is understood. If you are setting up an event action for a view that you have only just created, it is highly recommended to monitor events in that view for at least a day before activating the action.

For example, if you are setting up an event action that creates tickets in a ticketing system, and the view you have chosen has hundreds of events per day, you may create extra work and issues for fellow team members.

You can monitor events in a view from the events page, or you could also set up a low impact action first, such as sending an email to yourself or a message to a test channel in your messaging system.


Some actions require an integration, such as REST, ServiceNow, JIRA etc. If you wish to use one for your event action you will need to add the integration first from the Account > Integrations page. Currently, UpGuard supports integrations with PagerDuty, REST endpoints, ServiceNow, Slack, and Splunk.

Adding an Action

Once you’ve selected the view to use for your action, simply click the Add Action button to get started.

The first step is to choose the type of action you would like to set up. Currently, UpGuard supports the following:

If your action requires an integration you will need to select the relevant one. Specific details on each type can be found below.

Editing, Disabling, or Deleting an action

To edit an existing action navigate to the view it was created under and expand the Actions section. Click the Edit button to edit it.

The Edit button has a dropdown that also gives you the ability to disable, or delete the action.

Liquid Templating Syntax

Most action form fields support use of liquid syntax to introduce event variables.

{{ variable_name }} will insert a variable into a form field.

ServiceNow Action

Most elements in the ServiceNow action are fairly self explanatory, with a couple worth highlighting.

Record Type

The most common task types are included within UpGuard, but you can create records in other tables, including user-created tables, by selecting “Other” and then specifying the table name in the “Other Fields” text box.

"table": "u_my_custom_table"

Other Fields

The other fields input can be used to pass in values for any ServiceNow attribute you wish to set. Again, this is especially useful for user-generated fields:

"u_upguard_url": {{ node_url }}
Tags: events