Support Import

Event Log Monitor Trigger

The Windows Event Log is a Log that many programs write to when they start, stop, and/or fail. If you wish to monitor your Windows Event Log for some action, this is how you do it.

Custom Description:

A custom description that you want to set for this Trigger.

Event Log Name - Event Type - Event ID - Event Source:

You will be able to choose which Log you want to watch, and what type of Event to watch for (Information, Error, Warning, Audit Success, Audit Failure, or all of them). You can also choose the Event ID (an ID associated with a specific event) or the Event Source (a name chosen by the application, not necessarily its executable name - you will have to look through the Logs to find this possibly).

Event Message must (Not) contain:

Finally, you can set the Trigger to fire only for events that contain a specific text within their message or alternatively to ignore events that contain a specific text.

On trigger failure retry every

Optionally set a time period after which the Trigger will attempt to resume monitoring after encountering an error.


The Event Log Monitor Trigger, when fired, assigns values to five Trigger Variables that are made available to the Process:

%EventTriggerEventLogName% which will contain the name of the Log where the event was created,

%EventTriggerEventID% which will contain the Event ID of the event that was created,

%EventTriggerEventType% which will contain the type of the event that was created,

%EventTriggerEventSource% which will contain the source of the event that was created, and

%EventTriggerEventMessage% which will contain the message of the event that was created.

As you can have as many Triggers as you want attached to the same Process, this would allow you to know which Event fired the Process. You can access this information through Actions using those Variables.