FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
This article describes how to configure automatically respond to trigger events based on event log.

Automation stitches, actions, and triggers have separate dialogs and are no longer part of the main stitch dialog like previous versions.
When creating a stitch, select 'Add Trigger' and 'Add Action' displays a list of available triggers and actions, and the option to create a new one.

Once the stitch is configured, a process diagram of the trigger, actions, and delays are displayed.

To configure trigger .

- Go to System -> Automation, select trigger and select 'Network Down'. Select the below events
- Select 'Link monitor status, if link monitor is configured.
- Select 'Routing information changed', if SD-WAN is configured with performance SLA.

To configure action.

Go to System -> Automation, select 'Action' and select 'Default Email'.
To specify the mail where the event should be sent, Subject.

To configure automation stitch in CLI , execute the below commands
# config system automation-stitch
    edit "Network Down"
        set description            <----- Default automation stitch to send an email when a network goes down.
        set status enable
        set trigger "Network Down"
# config actions
    edit 1
        set action "Default Email"
To configure Automation trigger, execute the below commands.
# config system automation-trigger
    edit "Network Down"
        set description            <----- Default automation trigger configuration for when a network connection goes down.
        set event-type event-log
        set logid 22922 22921
To configure Automation stitch , execute the below command.
# config system automation-action
    edit <action-name>
        set action-type email
        set email-from <Email sender name>
        set email-to <email-address>
        set email-subject <subject-name>
        set minimum-interval <seconds>
Related document: