Skip to main content

Hourly Trigger

Run an automation on a repeating hourly interval, with optional conditions to filter which devices are included.

Updated this week

Introduction

The hourly trigger fires an automation repeatedly on a fixed interval — every 1, 2, 3, 4, 6, 8, or 12 hours. Use it for checks or tasks that need to run frequently throughout the day, like polling for a specific condition or applying a remediation that should retry regularly.

ℹ️ NOTE: Adding non-manual triggers requires either admin status or a role with the Manage automations permission. If you can see the automation but can't add triggers, check your role's permissions with your admin. See Workspace → Permissions for details.


Hourly Trigger

Hourly Trigger

Interval

Select how often the trigger fires using the Interval (in hours) dropdown.

Available intervals: 1, 2, 3, 4, 6, 8, 12 hours.

Condition

The Condition field determines which devices the trigger applies to each time it fires. You must select a condition to save the trigger — choose All devices to run against your entire inventory, or pick a more specific condition type to narrow the scope.

For the full condition reference (types, operators, values, and AND logic), see Trigger Conditions.

Additional Options

Expand Additional options to set an optional Trigger name and toggle the trigger on or off with the Enabled switch.

  • Trigger name — Replaces the default label on the pipeline trigger card. Useful when an automation has multiple triggers and you need to distinguish them at a glance.

  • Enabled — When off, the trigger won't fire. Existing in-progress runs are unaffected.


FAQ

  • Does the hourly trigger start from when the automation was created, or from midnight? Intervals are anchored to midnight, not to when the automation was created or last enabled. A 6-hour trigger fires at 0:00, 6:00, 12:00, and 18:00 regardless of when it was configured. A 1-hour trigger fires at the top of every hour.

  • What happens if a device is offline when the hourly trigger fires? It gets queued and will run when it comes back online. Missed fires don't stack — the device runs once when it reconnects. To exclude offline devices entirely, add a Status = Online condition. See Trigger Conditions for details.

  • Can I run an automation more frequently than every hour? The hourly trigger's minimum interval is 1 hour. For sub-hourly execution, use a script or monitor-based trigger instead.

  • Who can add or edit triggers on an automation? Admin users can always add triggers. Non-admin users need the Manage automations permission on their role, plus access to the automation's group. One exception: if an automation has no triggers at all yet, any user with group access can add the first one.

Did this answer your question?