How AgentiX playbooks are actually triggered: automation rules, jobs, and the WHEN/IF/THEN model.

In Cortex XSIAM, a playbook does not run by itself. Three things trigger it: automation rules (issue-driven), jobs (time or feed-driven), or a manual run. Understanding the trigger layer is the difference between automation that ships and automation that sits in a folder.

6 min read·Cortex XSIAM

Cortex XSIAM ships hundreds of detection rules already mapped to MITRE ATT&CK and tuned by Palo Alto Networks against telemetry from across their customer base. The work in week one is enabling the right ones, not authoring from scratch.

When a deployment SOW prices six weeks of rule tuning, half of that scope is reading the OOTB ruleset, deciding which to enable, and toggling them on. That work is genuinely valuable, but it is hours, not weeks. The other half, customizing rules to your environment specific noise, is real engineering and worth your partner full rate.

The trap is letting both halves get billed at the same engineering rate. Your team sees a six-week scope, assumes it is all custom work, and pays accordingly.

Read the full lesson with Pro.

The takeaways below are public so you know what is in the lesson. The full body, the negotiation script, and every other lesson unlock with Pro. Free 30 days, no card.

Start free 30-day trial →Sign in

Takeaways

→AgentiX uses WHEN/IF/THEN: a trigger fires, conditions filter, an action runs (playbook, Quick Action, or AI agent).
→Automation rules trigger only on initial ingestion, default to Medium+ severity, and execute in priority order (first match wins).
→Jobs trigger on time (cron) or on a feed change, with queue-handling settings (don't trigger, cancel previous, or run concurrently).
→AI agents require LLM capabilities enabled in the tenant; without them, agent-triggered rules fail.
→Order rules from specific to generic; the first match wins, so a generic catch-all above a specific rule swallows the matches.
→Bring a partner in for multi-system integrations, compliance-regulated playbook design, or custom AI agent governance.

Source: Create an automation rule (Palo Alto Networks docs)Last verified Apr 26, 2026

Copy-ready script

Pro

“Can you split the rule scope into two phases? Phase one is enablement of the OOTB ruleset against my environment, ideally on a flat-rate or fixed-fee basis. Phase two is authoring custom rules where the OOTB set has gaps, billed hourly.”

Unlock with Pro →

See it in your own quote.

Paste a Palo Alto Networks quote. The engine will tell you, line by line, where the pattern in this lesson actually shows up.

Have Clarify read your SOW