🧡 Skip to main content🔍 Skip to search

When Service Monitor starts executing a workflow, it makes service related variables available to the just started workflow instance. Kernel and file system drivers operate exactly in the same way as services.

Executable Fully qualified path to the service executable including arguments that were passed during the service startup.
  • C:\Windows\System32\svchost.exe -k netsvcs -p
  • \SystemRoot\system32\drivers\wcifs.sys
Service name A short service name that uniquely identifies the service.
  • BITS
  • wcifs
Display name A friendly or display name of the service.
  • Background Intelligent Transfer Service
  • Windows Container Isolation
Current status The status of the service at the time of triggering. The status variable contains one of the following values:
  • Starting
  • Running
  • Pausing
  • Paused
  • Resuming
  • Stopping
  • Stopped
  • Uninstalled
  • Unknown
Adjust()Streamline creation of Task workflows even further—instantly make quick variable adjustments such as in-place replacement (all, first, or last occurrence), trimming (whitespaces, quotes, etc.), or changing capitalization. Optionally, set a different display name.


Complex workflows often incorporate multiple Service Monitor Triggers. Are you wondering how to pull dynamic variables from the Trigger which set your workflow in motion? Or perhaps you need to pull data from any given Trigger, regardless of the activation criteria?

With the multi-triggering feature, keeping track of specific system services' statuses is easygoing and direct—simply fetch the values from Any Service Monitor category—and Automation Workshop will seamlessly connect your Actions with the right triggering data, ensuring a smooth operation without any extra effort. Experience immediate automation advantages across both local servers and distant machines!

Need help?

If you have any questions, please do not hesitate to contact our support team.