This article describes how to configure FortiGate to automatically respond to various trigger events. This article is for FortiOS 7.0 and 7.2 - the automation workflow was redesigned to be more efficient and clearer for the user.
Automation stitches, actions, and triggers have separate dialogs and are no longer part of the main automation stitch dialog like in previous FortiOS versions (6.2, 6.4).
1) When creating a stitch, selecting 'Add Trigger' or 'Add Action' displays a list of available triggers and actions, and also the option to create new ones.
2) Once the stitch is configured, a process diagram of the trigger, actions, and delays is displayed.
Notice the 'Action execution' options - it allows to choose if additional actions are executed in a specific order ('Sequential') or simultaneously ('Parallel'). If you choose 'Sequential', it is possible to configure a delay between actions in seconds ('Add delay' button). However, if one of the actions fails, then the next actions will not be executed and the automation stitch will stop.
Not all the triggers can be edited if based on some singular FortiOS event, e.g. reboot or failover.
The trigger can be also configured as a recurring schedule (hourly, daily, etc) for a specific action:
Other possible triggers:
To configure an action or update an existing one:
Another popular activity is running a CLI script - for example, it can be used to restart a process if automation gets triggered by 'High CPU' or 'Conserve Mode' triggers. To configure it, chose 'Create New' on the Action page and find 'CLI Script':
The commands can be either specified manually or recorded in the console widget.