Triggers
Triggers cause a workflow to execute. To add a trigger to a workflow, choose Automate > Triggers in the navigation menu.
The Triggers page includes these tabs:
-
-
Configure a rule that determines when a workflow is executed, such as when an event occurs or following a timetable. Add optional conditions, and if they're met, any workflow you've associated to use that rule as a trigger will be executed.
-
Examples of events include an approval task being approved, an email arriving in an inbox, a notification from Cisco XDR of a new incident, and a webhook being received. Use rules to watch for patterns in these services, thereby enabling policy-driven automation.
-
-
History
-
Shows a log of events that occurred and triggered any of your matching automation rules during the past 72 hours.
-
Table columns show the event name, type of event, number of automation rules that matched, and when the event occurred.
-
Search for and filter events by name, type, and timeframe during which they occurred (the past 24, 48, or 72 hours).
-
Click an event to slide out a drawer with additional details such as the raw event data and links to the matched rules and workflows executed (runs).
-
Events may not appear in the table if a per-day or per-minute rate limit was reached.
-
-
Events
-
Event definitions are being deprecated.
-
Instead, click on the Automation Rules tab and create a new rule. Select a rule type, fill in the respective criteria, and select the workflows to execute.
-
-
-
Calendars define a collection of days and times when a workflow should be executed.
-
A time range calendar can be used to trigger a workflow on pre-defined days and times.
-
-
-
Webhooks allow you to push information from external platforms to Automation workflows.
-
Instead of configuring your workflow to reach out to an API to check for events, you can configure a webhook to listen for incoming data and then trigger a workflow through an automation rule when data is received.
-