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.
Optionally, if you select Hours, you can set excluded time windows when the Schedule trigger won’t run. Under Excluded time windows, click the time picker icon 
to exclude times in the From: and To: fields. Click + Add excluded time window to add as many as needed.
Excluded time windows are ideal for avoiding maintenance windows or peak business hours. Note that excluded time windows can’t overlap.
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.
To create an API key for the Workflows API, on top right of any Workflows page, click the Configurations icon 
> Create API Key. 
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 Azure DevOps Listener
The Azure DevOps Listener allows you to receive real-time updates to ADO work items, and helps you integrate your incident response and ticket-based remediation into the DevOps lifecycle.
To use the Azure DevOps Listener in your flow:
In the Start node, from the Service dropdown, select Azure DevOps.
From the Integration dropdown, select an integration.
From the Event Type dropdown, select an event type.
In the Project Name field, enter a project name.
Under Filter Mode > Parameters, enter a Field name, select a Condition, and enter a Value as needed.
Optionally, under Filter Mode, click WIQL to filter, search, and retrieve specific work items. Enter specific filter conditions as needed. For example:
[System.TeamProject] = 'MyProject', [System.State] = 'Active')Optionally, add variables as needed.
In any downstream step input field, open the variables dropdown and select Start > event to add variables as needed.
Use case examples:
Trigger a flow every time a bug in an ADO work item is moved to the "Active" state to immediately notify your on-call team via Slack.
Capture the latest work notes from an ADO work item to automatically update a linked ticket in an external platform like Jira Service Desk, Zendesk, etc.
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.
Optionally, add variables as needed.
In any downstream step input field, open the variables 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.
Optionally, add variables as needed.
In any downstream step input field, open the variables 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.
Use Jira Service Desk Listener
The Jira Service Desk Listener allows you to receive real-time updates to Jira issues, and helps you integrate your incident response and ticket-based remediation into your ITSM lifecycle while working within Jira’s REST API capabilities.
To use the Jira Service Desk Listener in your flow:
In the Start node, from the Service dropdown, select Jira Service Desk.
From the Integration dropdown, select an integration.
From the Event Type dropdown, select an event type.
Under Filter Mode > Parameters, enter a Project name, Issue Type, Status, Assignee, and Priority.
Optionally, under Filter Mode, click JQL to filter, search, and retrieve specific work items. Enter specify filter conditions as needed.
Optionally, add variables as needed.
In any downstream step input field, open the variables dropdown and select Start > event to add variables as needed.
Jira Service Desk variables display in the following format: {{Start.event.<variable>}}
For example, a variable named “action_type” will display as: {{Start.event.action_type}}
Use ServiceNow Listener
The ServiceNow Listener allows you to receive events from your ServiceNow user devices.
To use the ServiceNow Listener in your flow:
In the Start node, from the Service dropdown, select ServiceNow.
From the Integration dropdown, select an integration.
From the Event Source Table dropdown, select an event source.
From the Event Type dropdown, select an event type.
Optionally, add filters as needed.
Optionally, add variables as needed.
In any downstream step input field, open the variables dropdown and select Start > event to add variables as needed.
ServiceNow Listener variables display in the following format: {{Start.event.<variable>}}
For example, a variable named “sys_id” will display as: {{Start.event.sys_id}}
Use case examples:
A new incident is opened in ServiceNow for an event triggered by an update.
Escalate remediation issues based on live ServiceNow activity.
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.