> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/automations-and-custom-objects/automations.md).

# Automations

Automations is a no-code workflow builder built directly into Shade. You define rules for what should happen when something occurs in your drive, and Shade runs them automatically in the background - no third-party tools and no code required.

Every automation is made of a **trigger** (the event that starts it) and one or more **actions** (what Shade does in response). You build automations using a visual, block-based editor.

{% embed url="<https://youtu.be/PIK9cQBpcSE?si=f7nBru4WD7SK9zjY>" %}

### How Automations Work

* Choose a **trigger** - the event that starts the automation
* Add one or more **actions** - chained together to run in order
* Save it, and the automation runs automatically whenever the trigger fires

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2F1Cs5qy7BCtq7vD9CF9ws%2FAutomations%200.gif?alt=media&#x26;token=2405d772-6b17-475a-bf76-1d790e788786" alt=""><figcaption></figcaption></figure>

### Triggers

Triggers are events in your drive. They're grouped in the editor like this:

* **Manual:** Manual Trigger
* **Files:** Asset Uploaded, Asset Downloaded, Asset Updated (when metadata changes, optionally a specific field and value), Asset Renamed, Asset Removed, Asset Deleted
* **Collections:** Asset Added to Collection, Asset Removed from Collection, Collection Created, Collection Updated, Collection Deleted
* **Custom objects:** Record Created, Record Updated
* **Share Links:** Share Link Created, Share Link Deleted
* **Comments:** Comment Added, Comment Updated, Comment Deleted, Comment Resolved, Comment Reacted
* **People:** Person Recognized
* **Proxies, previews, and transcription:** Transcription Completed, Video Proxy Completed, Audio Proxy Completed, Metadata Extracted
* **Network:** Webhook Received

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FgJ0O6bl6f3RcYwf7OiQT%2FAutomations%201.gif?alt=media&#x26;token=c75a9235-0f85-4406-8a86-46711e69e581" alt=""><figcaption></figcaption></figure>

### Actions

Actions are, in general, the things you can already do in Shade by hand. They include:

* **Logic:** Filter, If / Else, Switch
* **Files:** Create folder, Rename Asset, Move Asset, Update Asset Metadata
* **Share Links:** Generate Share Link, Generate Folder Share Link, Generate Collection Share Link
* **Collections:** Add to Collection, Remove from Collection, Rename Collection, Create Collection, Delete Collection
* **Custom objects:** Create Record, Find Record, Update Record, Delete Record, Get Record
* **Text:** Transform Text
* **Calculations:** Random Number, Adjust Time
* **Network:** Send HTTP Request
* **Other:** Send Email, Save Files to Drive

**Send Email** sends a message to a recipient with the subject and body you write. The body supports basic HTML formatting.

**Webhook Received** starts an automation when another service sends a request to its webhook URL, and **Send HTTP Request** calls an external URL from any step. For setup, authentication, and request details, see [Webhooks in automations](https://academy.shade.inc/developers/webhooks#webhooks-in-automations).

<figure><img src="https://450378260-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2F95JU1hzganNGVCaP7Pgc%2FAutomations%202.gif?alt=media&#x26;token=bea74699-1295-47a0-bb5f-75eb3a05b6e7" alt=""><figcaption></figcaption></figure>

### Building an Automation

Build an automation with the visual, block-based editor:

* Create a new automation
* Select your trigger (for example, **Asset Added to Collection**) and point it at the relevant collection
* Add your actions in the order they should run (for example, **Generate Share Link** -> **Send Email**)
* Save

### Example Workflows

* **Two-stage approvals:** When an asset’s **Approval Status** changes to **In review**, automatically generate a share link and email the internal reviewer. When it flips to **Approved**, send the finalized share link to the external reviewer - two stages, zero manual handoff.
* **Delivery package generator:** When assets move to **Ready to deliver** (or get added to a Delivery collection), automatically generate the right share link(s) and send a delivery email containing the links, included assets, and any notes. This turns “export + send links” into a single status change.
* **Intake routing:** When a file is uploaded to an incoming folder, use an **If / Else** block to check its metadata, then move it to the right project folder, update its metadata, and add it to a review collection - so new media lands where it belongs without manual sorting.


---

# 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://academy.shade.inc/automations-and-custom-objects/automations.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.
