> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-customization/indicator-layouts/add-a-script-in-the-indicator-layout.md).

# Add a Script in the Indicator Layout

Add automation script content to indicator layouts in Cortex XSOAR 6.15.

You can add content to the indicator **Summary** tab based on an automation script. To do this, you need to add the **General Purpose Dynamic Section** when editing indicator layouts.

The **General Purpose Dynamic Section** enables you to configure a section in the **Summary** tab from an automation script. The automation can return simple text, Markdown, or HTML; the results appear in the General Purpose Dynamic Section.

You can add any required information from an automation. For example:

* Add a mapping script that determines where an IP address originates and displays it on a map.
* Add a custom widget to the indicator page. The procedure is similar for indicators and incidents.
* Add the **FeedRelatedIndicator** script from the **Automation** page, which contains information about the relationship between an indicator, entity (such as malware), and other indicators (such as a MITRE ATT\&CK indicator), and connects externally to those indicators, if relevant.

Before you begin, create an automation script.

1. Select the indicator type or layout you want to add to the General Purpose Dynamic Section by completing steps 1 or 2 in [Customize an Indicator Type Layout](/cortex-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-customization/indicator-layouts/customize-an-indicator-type-layout.md).
2. Drag and drop the **General Purpose Dynamic Section** onto the page.
3. Select the General Purpose Dynamic Section, click <img src="https://content.gitbook.com/content/BpHpUTEMW1LJCAHPgrpq/blobs/D0RkdoVxbWUcUS9OA7CI/2427680254fbfabedc1a6c93ddc3e71cf6c49450c3dca13432bac2abe45eb4db.png" alt="indicator-option-pointer.png" data-size="line"> and then click **Edit section settings**.
4. In the **Name** and **Description** fields, add a meaningful name and a description for the dynamic section that explains what the script displays.
5. In the **Automation script** field, from the dropdown list, select the script that returns data for the dynamic section.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Only automations to which you have added the dynamic-indicator-section tag appear in the dropdown list.</p></div>
6. Click **OK**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-threat-intel-management-guides/6.15/configure-indicators/indicator-customization/indicator-layouts/add-a-script-in-the-indicator-layout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
