> 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

<figure><img src="/files/iGYBI6axhxx13OpFwnoi" alt=""><figcaption><p>An example Response Action</p></figcaption></figure>

\### 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 avaiable 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 %}