# Actions

#### The action object

Both Schedule automations and Event automations require actions. Actions are passed as JSON objects in an array. See the [Scheduled Automations](/administration/automations/scheduled-automations.md) nad [Event Automations](/administration/automations/event-automations.md) docs to see how to include them when configuring the automations .

Here is an example of what an action object looks like.

```json
[
    {
        "type":"<action_type>",
        ....
    }
]
```

Actions have variable params, which can be found below. An example of a copy action is here

```
{
    "type":"copy",
    "copy_to":"/new/destination/"
}
```

#### Available Action Types

As of writing this document, we support the following action types.&#x20;

| Action Type  | Description                            |
| ------------ | -------------------------------------- |
| webhook      | Fire a webhook of to a remote endpoint |
| rename       | Rename the file                        |
| delete       | Delete the file                        |
| copy         | Copy/duplicate the file                |
| move         | Move the file to a new location.       |
| email        | Send an email notification             |
| compress     | Compress the file                      |
| decompress   | Decompress the file                    |
| unarchive    | Unarchive the file                     |
| pgp\_encrypt | Encrypt the file with PGP              |
| pgp\_decrypt | Decrypt a file encrypted with PGP      |


---

# Agent Instructions: 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:

```
GET https://developers.couchdrop.io/administration/automations/actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
