Skip to content

Synchronize Alerts with an external tool

This use case describes how to automatically push new Alerts in an external security tool such as SIRP, SOAR or EDR etc.


  • A XDR licence
  • The user that configures the Playbook should have a Role that contains:
    • The SYMPHONY permissions
  • An API Key with a Role that contains at least the following permission:

To create your API Key, follow this documentation.

Playbook creation

First create a new playbook by following those steps:

  • Go to the Playbook page
  • Click on + PLAYBOOK
  • If multi-tenant is available, select the Community where the Playbook should be executed
  • Select the option Create a playbook from scratch
  • Select the block Alert Created

The Playbook will automatically be executed when a new alert is created in

Playbook configuration

  1. Configure the Alert Created block

  2. On the right panel, under the Module Configuration section, click on + Create new configuration

  3. Complete the form with the following information:
    • Name: ReadAlertContent
    • Base_url:
  4. Click on the Save button

  5. Get Alert information

  6. On the left panel, search for the Get Alert block

  7. Drag and drop it underneath the Alert Created block
  8. On the right panel, select the ReadAlertContent configuration previously created
  9. Select the Alert Created block and click on alert_uuid copy icon
  10. Select the Get Alert block and past the content in the Configuration section, on the uuid cell
  11. Link the trigger Alert Created to the action module Get Alert

  12. Make HTTP Requests

  13. On the left panel, search for the Request URL block

  14. Drag and drop it underneath the Get Alert block
  15. On the right panel, complete the form with the following information:

    • JSON: {"alert_short_id":"{{ node.0['alert_uuid'] }}", "rule_name":"{{ node.1['rule']['name'] }}","rule_severity":"{{ node.1['rule']['severity'] }}","description":"This is a description"}
    • Method: post
    • Headers: {"Authorization": "Bearer YOUR_EXTERNAL_PRODUCT_API_KEY_NOT_THE_SEKOIAIO_ONE"}


Please replace the headers by following your third party product documentation.

Your playbook should look like the following:

Playbook Use Case

Your Playbook is ready

  • Save your Playbook by clicking on the SAVE button on the center of the page
  • Activate your Playbook by toggling the value from Off to On, on the top right of the page

See your Playbook runs

  • On the top right of the page, click on Runs
  • Confirm the displayed Status is Succeeded
  • If you click on a run from the history, you will be redirected to the Graph page. Then you will be able to see the results of each block by clicking on it, as of the following picture:

Playbook History


To highlight this specific example, we tested to send a message with alert metadata to a simple Custom format Intake of made for this occasion on a personal Community. With the same playbook logic, we only changed the Request URL block configuration parameters as following: * JSON:

{"json":"'{\"alert_short_id\":\"{{ node.0['alert_uuid'] }}\", \"rule_name\":\"{{ node.1['rule']['name'] }}\",\"rule_severity\":\"{{ node.1['rule']['severity'] }}\",\"description\":\"An HTTP request was made from Playbook\"}'",
* Method: post * URL:


Those configuration parameters were filled-in by following this documentation.

The result is an event received on in a dedicated Intake, with the content of the POST request that was mapped in the relevant ECS fields (thanks to the Custom Format) mandatory to display a SMART Description.

Display the Request