> For the complete documentation index, see [llms.txt](https://docs.dropzone.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dropzone.ai/platform/settings/response-actions.md).

# Response Actions and Automations

*Available to Admins only*

**Response Actions** (also referred to as Response Automations) allow you to automatically execute custom Python code when investigations complete. This enables seamless integration with external systems and consistent, repeatable response workflows.

Response Actions are commonly used to:

* Notify external systems
* Trigger remediation workflows
* Enrich tickets or records
* Apply policy-driven actions at scale

## The Response Action Page

The Response Action page is located in the left navigation under AI Setup & Tuning.

<figure><img src="https://435022081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBVcKuiytGCsIDpL70BC%2Fuploads%2Fgit-blob-c92e627a8e582b54cee1e9678e236d4519725724%2Fui-response-actions-page.png?alt=media" alt=""><figcaption><p>The Response Action Page</p></figcaption></figure>

Here you can:

1. See a complete list of all your configured Response Actions
2. See every time a response action has run, including execution results and errors
3. Manage configured Response Actions
4. Create Response Actions based off pre-configured templates
5. Create Custom Response Actions
6. Store API Keys and Secrets in our secure Secrets Manager

### How Response Automations Work

#### Execution Model

* **Trigger Events**\
  Dropzone has over 50 triggers to fire your Response Action. These range from Investigations complete with a specific status to a change of an API key.
* **Sandboxed Environment**\
  Code runs in an isolated container using **Python 3.11**.
* **Data Injection**\
  Investigation context and stored secrets are injected automatically as Python dictionaries. You can use the example script here to see the investigation variable and all information available to you using Response Actions.

{% hint style="info" %}
The variables available can change depending on the trigger you use. Keep this in mind when planning/creating Response Actions.
{% endhint %}

* **Result Capture**\
  All output, errors, and execution status are logged for auditing and troubleshooting.

{% hint style="info" %}
Want to learn more? Check out our [**Building Reponse Automations and Actions Best Practices Guide**](/best-practices/how-to-build-response-automations-and-actions.md)
{% endhint %}