You can select one of the following trigger types to activate the Start node in a workflow:
Schedule
The Schedule trigger type enables you to automate the execution of the workflow based on a predefined schedule. You can configure the schedule with the following options:
Interval
Under Repeat every, select one of the following time intervals:
Minutes
Hours
Days
Based on your selection, more fields appear to enable you to specify when to run your flow.
Specific time
Under Specific time, select one of the following recurrences:
Daily. Set a Time and Timezone.
Weekly. Select at least one day of the week, set a Time and Timezone.
Use case examples:
Running a daily health check on all critical servers at 3:00 AM.
Generating a weekly performance report every Monday morning.
Monthly offboarding of temporary user accounts on the last day of the month.
API
The API trigger type exposes a unique API endpoint for your workflow. Other applications, services, or scripts can then initiate this workflow by sending an HTTP request to this endpoint.
Use case examples:
Triggering a system remediation workflow automatically when an alert is fired by a monitoring system.
Initiating a user provisioning workflow from an HR management platform.
Allowing a custom web application to trigger a specific IT automation task.
Manual
Selecting the Manual trigger type means that the workflow executes only when a user explicitly starts it. This is done in the Workflow application’s Flows tab by clicking the actions menu and selecting Run Manually.
Use case examples:
Running a script to onboard a new employee when the HR paperwork is complete.
Executing a diagnostic workflow on a specific machine when a user reports an issue.
Generating an on-demand report.
Listener
The Listener trigger type allows you to activate your flow based on alerts received from ControlUp for Desktops, Jamf Pro, or ServiceNow. You select a specific service and an available alert. When the alert is triggered, your flow executes.
Use ControlUp One Platform Listener
The ControlUp One Platform Listener allows you to receive alerts from your user devices with ControlUp for Desktops.
To use the ControlUp One Platform Listener in your flow:
In the Start node, from the Service dropdown, select ControlUp One Platform.
From the Integration dropdown, select an integration.
From the Alert dropdown, select an alert and click Save. This makes the service’s variables available to use in downstream steps.
In any downstream step input field, open the dropdown and select Start > event to add variables as needed.
ControlUp One Platform Listener variables display in the following format: {{Start.event.<variable>}}
For example, a variable named “action_type” will display as: {{Start.event.action_type}}
Use Jamf Pro Listener
The Jamf Pro Listener allows you to receive events from your Jamf user devices.
To use the Jamf Pro Listener in your flow:
In the Start node, from the Service dropdown, select Jamf Pro.
From the Alert dropdown, select an alert and click Save. This makes the service’s variables available to use in downstream steps.
Follow the instructions displayed under the alert to setup a webhook in the Jamf settings. You must configure a separate webhook in Jamf for each event that you want to listen to, as Jamf does not support sending multiple events to a single URL via one webhook.
In any downstream step input field, open the dropdown and select Start > event to add variables as needed.
Jamf Pro Listener variables display in the following format: {{Start.event.<variable>}}
For example, a variable named “action_type” will display as: {{Start.event.action_type}}
Use case examples:
Automatic responses to security incidents by generating incident tickets using collected data - no manual user input required.
Service health monitoring and escalation based on diagnostic results from affected systems.
Interactive troubleshooting sends diagnostic options to your IT support team via a chat service, waits for their input, and then automatically applies their selected fixes to the affected systems.
Form
The Form trigger type allows you to activate your flow when a user submits an existing form. The flow is activated automatically based on the input provided in the selected form.
To use Form variables in your flow:
In the Start node, from the Form name dropdown, select the desired form and click Save. This makes the form’s variables available to use in downstream steps.
In any downstream step input field, open the dropdown and select Start to add Form variables as needed.
Form variables display in the following format: {{Start.<form variable>}}
For example, a variable named “User Name” will display as: {{Start.User Name}}
Use case examples:
Onboarding new employees.
Responding to user survey submissions.
Evaluation and remediation of incident reports results.