Automation conditions

Conditions let you control exactly when an automation runs, instead of letting it fire on every matching event. This article is for anyone setting up or fine-tuning automations in InfraNest.

#Overview

• Without conditions, a rule runs on every event that matches its trigger.
• With conditions, the rule only runs when the event's details also match what you've set.
• All conditions must match — they're combined with and by default (you can mix in or using groups).

#Add a condition to a rule

1. Open the automation and go to where you build it.

2. Select Add condition.
3. Choose the Field you want to check. The fields available depend on the trigger you picked — for example, a domain-expiring event offers fields like Days left, while a monitor event offers fields like Check name and Monitor status now.
4. Choose an Operator — options include equals, not equals, contains, doesn't contain, greater than, greater or equal, less than, less or equal, is one of, is not one of, is set, and is not set.
5. Enter the Value to compare against. You can type a fixed value, or use Insert value to reference a placeholder from the event itself (or from Earlier values) — this lets you compare one field to another, or to the current date/time.
6. Repeat to add more conditions. Remember, every condition you add must match for the rule to run.
7. Select Save automation when you're done.

NoteLeave the conditions list empty if you want the rule to run on every matching event.

#Build an "this or that" rule with groups

1. In the conditions area, select Add group.
2. Set the group's own Match toggle to Any (to mean "or") or All (to mean "and") — this controls how the conditions inside that group are combined.
3. Add the relevant conditions inside the group using Add condition.
4. Add more groups if needed — groups can be nested, so you can combine an All group with an Any group to express something like: (days left is less than 14 and tags contains production) or (certificate status equals expired).
5. Select Remove group next to any group you no longer need.
6. Select Save automation to apply your changes.

#Limit a rule to certain times

1. Add a condition using one of the built-in time fields: Weekday (0 is Sunday), Hour of day (0–23), or Weekend.
2. Choose an Operator, such as equals or greater or equal, and enter the Value — for example, Hour of day (0–23) greater or equal 18 to only act after 18:00.
3. Combine this with other conditions if needed, using groups if you want "or" logic.
4. Select Save automation.

TipTime-based fields are evaluated in InfraNest's timezone, so double-check the time zone if a rule seems to run at an unexpected moment.

#Tips

• Use Test run or Test run (dry run) after setting up conditions to confirm the rule would — or would not — have acted on a sample event, without it actually firing.
• Keep conditions as simple as possible at first; you can always add more using Add condition or Add group later.

#Troubleshooting

• The rule never runs: Check that every condition can actually be true at the same time — remember they're combined with and unless you've grouped some with Any.
• The rule runs when it shouldn't: Look for a missing condition, or a group set to Any that's too broad — tighten it with All or add another condition.
• A field isn't available: The fields you can choose depend on the trigger. Check Automation triggers and actions to see which fields that specific trigger exposes.