> 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-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/add-objects-from-the-task-library/add-manual-tasks-and-blank-tasks.md).

# Add manual tasks and blank tasks

Add manual and blank tasks to a playbook.

Cortex Cloud supports task types for different playbook actions.

### Add a manual task

**Manual Tasks** lists playbooks in your Org repository and their manual tasks. These tasks do not run scripts and may require manual input.

By default, playbooks are sorted by their latest update. You can also sort playbooks alphabetically.

{% stepper %}
{% step %}
In the **Task Library** pane, select **Manual Tasks**.
{% endstep %}

{% step %}
Select a playbook to view its tasks.
{% endstep %}

{% step %}
Drag the required task onto the playbook editor.
{% endstep %}

{% step %}
Connect the added task by dragging a wire to it.
{% endstep %}

{% step %}
Save the playbook.
{% endstep %}
{% endstepper %}

A user icon identifies tasks that require manual input. Change the task settings to automate the task.

### Add a blank task

A **Blank Task** lets you create a custom task from scratch.

{% stepper %}
{% step %}
In the **Task Library** pane, select **Blank Task**.
{% endstep %}

{% step %}
In the **Task Details** pane, select a **Task Type**.

* **Standard task** — Confirm information or escalate a case.
* **Conditional task** — Validate values or parameters and direct the workflow.
* **Data Collection task** — Collect information from users in your organization.
* **Section Header** — Group related tasks and organize the playbook flow.
  {% endstep %}

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

{% step %}
Configure settings for the selected task type.

See [Add objects from the Task Library](/cortex-xsiam/configure-cortex-xsiam/automations/playbooks/build-your-playbook/add-objects-from-the-task-library.md) for task type details.
{% endstep %}

{% step %}
Select **Save**.

The task is added to the playbook editor.
{% endstep %}

{% step %}
Connect tasks in their logical order by dragging a wire between them.
{% endstep %}

{% step %}
Save the playbook.
{% endstep %}
{% endstepper %}


---

# 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-cloud-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/add-objects-from-the-task-library/add-manual-tasks-and-blank-tasks.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.