> 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/demisto-sdk-development-guide/demisto-sdk-guide/demisto-sdk-commands/run-playbook.md).

# run-playbook

This command runs the given playbook in Cortex XSOAR or Cortex XSIAM.

The `run-playbook` command requires interactions with Cortex XSIAM or Cortex XSOAR. Before using the command, verify the [environment variables](/demisto-sdk-development-guide/demisto-sdk-guide/install-demisto-sdk/environment-variables-setup.md) are set up.

<details>

<summary>Arguments</summary>

| Argument            | Description                                                                                                                    |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `-u, --url`         | URL to a Cortex XSOAR or Cortex XSIAM instance.                                                                                |
| `-p, --playbook_id` | The ID of the playbook to run.                                                                                                 |
| `-t, --timeout`     | Timeout for the command in seconds. The playbook will continue to run in Cortex XSOAR/Cortex XSIAM. The default is 90 seconds. |
| `--insecure`        | Skips certificate validation when authorizing Cortex XSOAR or Cortex XSIAM.                                                    |
| `-w, --wait`        | Waits until the playbook run is finished and get a response.                                                                   |

</details>

<details>

<summary>Examples</summary>

The following examples assume both the `DEMISTO_API_KEY` and `DEMISTO_BASE_URL` environment variables are set:

`export DEMISTO_BASE_URL = https://demisto.local`

`export DEMISTO_API_KEY = api key`

* `demisto-sdk run-playbook -p 'playbook_id'`

  This runs the playbook with `playbook_id` in the instance <https://demisto.local> and waits for the playbook to finish its run. If the run takes more than 90 seconds (the default timeout), the command stops while the playbook keeps running in Cortex XSOAR/Cortex XSIAM.
* `demisto-sdk run-playbook -p 'playbook_id' -n`

  This runs the playbook with `playbook_id` in the instance <https://demisto.local> and does not wait to see the response. The playbook keeps running in Cortex XSOAR/Cortex XSIAM.
* `demisto-sdk run-playbook -p 'playbook_id' -t 300`

  This runs the playbook with `playbook_id` in the <https://demisto.local> instance and waits for the playbook to finish its run. If the playbook runs for more than five minutes (300 seconds), the command stops while the playbook keeps running in Cortex XSOAR/Cortex XSIAM. For a long-running playbook, consider increasing the `timeout` argument.

</details>


---

# 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/demisto-sdk-development-guide/demisto-sdk-guide/demisto-sdk-commands/run-playbook.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.