> 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&amp;token=2405d772-6b17-475a-bf76-1d790e788786" alt=""><figcaption></figcaption></figure>

### Triggers

Triggers are events in your drive, including:

* A file is uploaded
* An asset is updated
* An asset is renamed
* A file is added to a collection
* An asset receives a specific metadata modification

<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&amp;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:

* Add a file to a collection
* Add a comment
* Create or update a **Custom Object** record
* Generate a share link
* Send an email notification (branded and customizable)

<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&amp;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, **File added to a 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 (optionally with a Slack ping) containing the links, included assets, and any notes. This turns “export + send links” into a single status change.
* **Rights/usage expiration enforcement:** On a daily schedule (or when a rights record updates), automatically find assets whose usage rights are expiring soon and alert the owner. When rights expire, automatically restrict external sharing (and optionally move assets to a restricted area) so expired media can’t keep circulating.


---

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