Great point- and you're absolutely right!
To avoid alert fatigue, we’ve built in several ways to add smart conditions to the Log Trigger step.
For example, you can ask the AI to trigger only on consecutive attacks, or define conditions like:
We’ve also recently added a powerful new condition that lets you filter logs based on IP Geo-location, using fields directly from the logs.
I’ve attached a few screenshots below so you can see it in action.
And regarding newly created AI automations, users can review, re-generate, and fully edit the automation at any time before enabling it.
Thanks again for raising this - it's an important consideration!
Count logs - distinct
Suppress logs
Count logs - occurrences by field
IP Geolocation - included/ excluded from specific countries
Many options for conditions on logs