DOCS-91 - Playbook payloads (#4650)

* First draft

* Second draft

* cid redirect

* Corrections

---------

Co-authored-by: Kim Pohas <[email protected]>

Author: jpipkin1

cid-redirects.json

@@ -2727,7 +2727,7 @@
   "/cid/21037": "/docs/integrations/google/cloud-vpn",
   "/cid/21038": "/docs/integrations/containers-orchestration/vmware-tanzu-application-service",
   "/cid/10999": "/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source",
-  "/cid/11000": "/docs/alerts/monitors/automation-payload-variables",
+  "/cid/11000": "/docs/platform-services/automation-service/automation-service-playbooks",
   "/Cloud_SIEM_Enterprise": "/docs/cse",
   "/Cloud_SIEM_Enterprise/Administration": "/docs/cse/administration",
   "/Cloud_SIEM_Enterprise/Administration/Cloud_SIEM_Enterprise_Feature_Update_(2022)": "/docs/cse/administration",
@@ -3412,6 +3412,7 @@
   "/Visualizations-and-Alerts/Alerts/02-Schedule-a-Search": "/docs/alerts/scheduled-searches",
   "/Visualizations-and-Alerts/Alerts/Alert_Grouping": "/docs/alerts/monitors/alert-grouping",
   "/Visualizations-and-Alerts/Alerts/Alert_Variables": "/docs/alerts/monitors/alert-variables",
+  "/docs/alerts/monitors/automation-payload-variables": "/docs/platform-services/automation-service/automation-service-playbooks",
   "/Visualizations-and-Alerts/Alerts/Monitors": "/docs/alerts/monitors",
   "/Visualizations-and-Alerts/Alerts/Monitors/About_Monitors": "/docs/alerts/monitors/overview",
   "/Visualizations-and-Alerts/Alerts/Monitors/Monitor_FAQ": "/docs/alerts/monitors/monitor-faq",

docs/alerts/monitors/automation-payload-variables.md

@@ -78,10 +78,4 @@ In this section, we'll introduce the following concepts:
   <p>Learn how to use Automation Service playbooks with monitors.</p>
   </div>
 </div>
-<div className="box smallbox card">
-  <div className="container">
-  <a href="/docs/alerts/monitors/automation-payload-variables"><img src={useBaseUrl('img/icons/operations/monitor-and-visualize.png')} alt="icon" width="40"/><h4>Automation Payload Variables</h4></a>
-  <p>Learn details about variables passed from a monitor to a playbook in the Automation Service.</p>
-  </div>
-</div>
 </div>

docs/alerts/monitors/index.md

@@ -155,7 +155,7 @@ Some integrations that have useful actions for monitors include:
 
 ### Pass custom fields from a monitor to playbooks
 
-Results from an alert query are passed to a playbook through the [automation payload](/docs/alerts/monitors/automation-payload-variables/). The variables from the payload can be used as inputs for different nodes in the playbook after they are defined as parameters in the start node.
+Results from an alert query are passed to a playbook through the [alert payload](/docs/platform-services/automation-service/automation-service-playbooks/#alert-payload). The variables from the payload can be used as inputs for different nodes in the playbook after they are defined as parameters in the start node.
 
 :::note
 You must use [alert grouping](/docs/alerts/monitors/alert-grouping/) in the monitor configuration to pass fields from the query to the playbook.
@@ -165,12 +165,12 @@ You must use [alert grouping](/docs/alerts/monitors/alert-grouping/) in the moni
 
 1. Click **Edit** on the Start Node.
 1. Select **Alert** from the dropdown. <br/><img src={useBaseUrl('img/alerts/parse_from_alert.png')} alt="Payload parameters from an alert" style={{border: '1px solid gray'}} width="700" />
-1. The parameters from the default [automation payload variables](/docs/alerts/monitors/automation-payload-variables/) will be defined, along with some placeholders for custom fields that may be passed from the alert query. To reference a field passed from the alert query, use `customPlaceholderMap[].FIELDNAME`.
+1. The parameters from the default [alert payload variables](/docs/platform-services/automation-service/automation-service-playbooks/#alert-payload) will be defined, along with some placeholders for custom fields that may be passed from the alert query. To reference a field passed from the alert query, use `customPlaceholderMap[].FIELDNAME`.
 
-#### Configure Parameters from a JSON Payload
+#### Configure parameters from a JSON payload
 
 1. Click **Edit** on the Start Node.
 1. Select **Parse from Json** from the dropdown. <br/><img src={useBaseUrl('img/alerts/parse_from_json.png')} alt="Payload parameters from a Json payload" style={{border: '1px solid gray'}} width="700" />
-1. Copy the payload from a previously triggered automation. You can view the playbook payload of a previously triggered alert by following the steps [here](/docs/alerts/monitors/automation-payload-variables/#view-playbook-payload).
+1. Copy the payload from a previously triggered automation. You can view the playbook payload of a previously triggered alert by following the steps [here](/docs/platform-services/automation-service/automation-service-playbooks/#alert-payload).
 1. Paste the payload into the **Enter Json payload** text box and click **Parse**. The fields from the payload will be auto parsed to parameters. <br/><img src={useBaseUrl('img/alerts/parse_from_json_payload.png')} alt="Parse from Json payload" style={{border: '1px solid gray'}} width="700" />
 1. Add or remove parameters based on the playbook requirements and click **Update**. <br/><img src={useBaseUrl('img/alerts/parse_from_json_parameters.png')} alt="Json Payload parameters" style={{border: '1px solid gray'}} width="700" />