> 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-cloud-runtime-security/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/add-objects-from-the-task-library/add-manual-tasks-and-blank-tasks/create-a-standard-task.md).

# Create a standard task

Standard tasks can require manual verification before automated actions continue. They can also automate actions, such as parsing files or enriching indicators.

{% stepper %}
{% step %}
From the **Task Library** pane, select a task.

For example, select **Blank Task**.
{% endstep %}

{% step %}
In the **Task Details** pane, select the **Standard** task type.
{% endstep %}

{% step %}
Enter a meaningful value in **Task Name**.

Use a name that describes the data you collect.
{% endstep %}

{% step %}
Configure the required Standard task options.\
Standard tasks include the following fields and tabs:<br>

<table><thead><tr><th width="256">Field / tab</th><th>Settings</th></tr></thead><tbody><tr><td>Choose script field</td><td><p>From a drop down list, select a script for the playbook to run. In the following tabs you can set:</p><ul><li><strong>Inputs</strong>: Each script has its own set of input arguments (or none). You can set each argument to a specific value (by typing directly on the line under the argument name) or you can click the curly brackets to define a source field to populate the argument.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>When a script or integration command requires a credential, such as a username/password or API key, you can typically select a stored secret by clicking <strong>Switch to credentials</strong>. If your user role has the <strong>Credentials</strong> permission set to <strong>None</strong>, this option is hidden and you will see the message <strong>Credentials are locked by admin</strong>. In this state, you cannot view, select, or reference any stored credentials within the task configuration.</p></div><ul><li><strong>Outputs</strong>: Each script has its own set of output arguments (or none).</li><li><p><strong>Mapping</strong>:</p><p>Map the output from a playbook task directly to an issue field.</p><p>The value for an output key populates the specified field per issue. This is a good alternative to using a task with the <code>setIssue</code> command.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>The output value is dynamic and is derived from the context at the time that the task is processed. As a result, parallel tasks that are based on the same output may return inconsistent results.</p></div><ol><li>In the <strong>Mapping</strong> tab, click <strong>Add custom output mapping</strong>.</li><li>Under <strong>Outputs</strong>, select the output parameter whose output you want to map. Click the curly brackets to see a list of the output parameters available from the script.</li><li>Under <strong>Field to fill</strong>, select the field that you want to populate with the output.</li><li>Click <strong>Save</strong>.</li></ol></li><li><p><strong>Advanced</strong>: Includes the following fields.</p><ul><li><strong>Using</strong>: Choose which integration instance will execute the command, or leave empty to use all integration instances.</li><li><strong>Extend context:</strong> Append the extracted results of the action to the context. For example, "newContextKey1=path1::newContextKey2=path2" returns "[path1:'aaa',path2: 'bbb', newContexKey1: 'aaa',newContextKey2:'bbb']"</li><li><strong>Ignore outputs:</strong> If set to true, will not store outputs into the context (besides the extended outputs).</li><li><strong>Execution timeout (seconds)</strong>: Sets the command execution timeout in seconds.</li><li><p><strong>Indicator Extraction mode:</strong> Choose when to extract indicators:</p><ul><li><strong>None</strong>: Do not perform indicator extraction</li><li><strong>Inline</strong>: Before other playbook tasks</li><li><strong>Out of band:</strong> While other tasks are running</li></ul></li><li><strong>Mark results as note</strong></li><li><strong>Mark results as evidence</strong></li><li><strong>Run without a worker</strong></li><li><strong>Skip this branch if this script/playbook is unavailable</strong></li><li><strong>Quiet Mode:</strong> When in quiet mode, tasks do not display inputs and outputs or extract indicators. Errors and warnings are still documented. You can turn quiet mode on or off at the task or playbook level.</li></ul></li><li><p><strong>Details</strong>: Includes the following fields.</p><ul><li><strong>Tag the result with</strong>: Add a tag to the task result. You can use the tag to filter entries in the War Room.</li><li><strong>Task description (Markdown supported):</strong> Describe what this task does. You can enter objects from the context data in the description. For example, in a communication task, you can use the recipient’s email address. The value for the object is based on what appears in the context every time the task runs.</li></ul></li><li><p><strong>On Error:</strong> Includes the following fields.</p><ul><li><strong>Number of retries</strong>: How many times the task should retry running if there is an error. Default is 0.</li><li><p><strong>Retry interval (seconds):</strong> How long to wait between retries. Default is 30 seconds.</p><p>The maximum retry interval is 800 seconds (13.3 minutes). If you enter a value greater than 800 seconds, the retry interval will be limited to 800 seconds.</p></li><li><p><strong>Error handling:</strong> How the task should behave if there is an error. Options are:</p><ul><li><strong>Stop</strong></li><li><strong>Continue</strong></li><li><p><strong>Continue on error path(s)</strong></p><p>This option configures the task to handle potential errors that may occur when executing the current task's script.</p></li></ul></li></ul></li></ul></td></tr><tr><td>Manual task settings tab</td><td><ul><li><strong>Default assignee:</strong> Assign an owner to this task.</li><li><strong>Only the assignee can complete the task</strong>: Stop the playbook from proceeding until the task assignee completes the task. By default, in addition to the task assignee, the default administrator can also complete the blocked task. You can also block tasks until a user with an external email address completes the task.</li><li><strong>Task SLA:</strong> Set the SLA in granularity of weeks, days, hours, and minutes.</li><li><strong>Set task Reminder at:</strong> Set a reminder for the task in the granularity of weeks, days, hours, and minutes.</li></ul></td></tr><tr><td>Advanced tab</td><td><ul><li><strong>Register as case timeline record</strong>: If enabled, the results of the task execution appear as a record in the case timeline. If enabled, you must enter a <strong>Record name.</strong> You have the option of adding an <strong>Effective time</strong>, <strong>Description</strong>, <strong>Tags</strong>, and marking the record as evidence and adding an evidence comment.<br>NOTE: Only enter an <strong>Effective time</strong> if you want the same exact time recorded every time the playbook task executes.</li><li><strong>Quiet Mode:</strong> Determines whether this task uses the playbook default setting for quiet mode. When in quiet mode, tasks do not display inputs and outputs or extract indicators. Errors and warnings are still documented. You can turn quiet mode on or off at the task or playbook level.</li></ul></td></tr><tr><td>Details tab</td><td><ul><li><strong>Tag the result with:</strong> Add a tag to the task result. You can use the tag to filter entries in the War Room.</li><li><strong>Task description (Markdown supported):</strong> Provide a description of what this task does. You can enter objects from the context data in the description. For example, in a communication task, you can use the recipient’s email address. The value for the object is based on what appears in the context every time the task runs.</li></ul></td></tr></tbody></table>
{% endstep %}
{% endstepper %}

5. Click **Save**.

   The task is added in the playbook editor.

   If you selected a system script in the settings, the task logo indicates **Built-in**.
6. Connect the tasks you've added in their logical order by dragging and dropping a wire from one task to another.
7. Save the playbook.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/add-objects-from-the-task-library/add-manual-tasks-and-blank-tasks/create-a-standard-task.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.