> 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/guides/automations.md).

# Automations

Recipes for automations that organize, share, and publish files for you when something happens in a drive.

Every recipe here is built in the no-code automation editor. If you haven't used it before, start with [Your first automation](/guides/automations/your-first-automation.md). It covers the editor basics the other recipes assume you know.

## Organize and share

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Your first automation</strong></td><td>Put every new upload into a "To review" collection.</td><td><a href="/guides/automations/your-first-automation.md">Your first automation</a></td></tr><tr><td><strong>Auto-organize new uploads</strong></td><td>Set metadata, rename, and move files the moment they land.</td><td><a href="/guides/automations/auto-organize-new-uploads.md">Auto-organize new uploads</a></td></tr><tr><td><strong>Tell a client their files are ready</strong></td><td>One right-click creates a share link and emails it to the client.</td><td><a href="/guides/automations/tell-a-client-their-files-are-ready.md">Tell a client their files are ready</a></td></tr><tr><td><strong>Get alerted when a person appears in footage</strong></td><td>Email yourself whenever a specific person is recognized in new media.</td><td><a href="/guides/automations/get-alerted-when-a-person-appears-in-footage.md">Get alerted when a person appears in footage</a></td></tr></tbody></table>

## Publish and connect other tools

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Publish to YouTube or Vimeo after approval</strong></td><td>Approved cuts upload themselves to your channel.</td><td><a href="/guides/automations/publish-to-youtube-or-vimeo-after-approval.md">Publish to YouTube or Vimeo after approval</a></td></tr><tr><td><strong>Turn long videos into social clips with Opus Clip</strong></td><td>Generate short clips from long-form video and save them back to your drive.</td><td><a href="/guides/automations/turn-long-videos-into-social-clips-with-opus-clip.md">Turn long videos into social clips with Opus Clip</a></td></tr><tr><td><strong>Batch-enhance photos with Topaz</strong></td><td>Upscale, denoise, or sharpen every photo dropped into a folder.</td><td><a href="/guides/automations/batch-enhance-photos-with-topaz.md">Batch-enhance photos with Topaz</a></td></tr><tr><td><strong>Connect Shade to other tools with webhooks</strong></td><td>Start automations from any tool, and send data out to any API.</td><td><a href="/guides/automations/connect-shade-to-other-tools-with-webhooks.md">Connect Shade to other tools with webhooks</a></td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://academy.shade.inc/guides/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 `build a script that syncs our docs to a CMS` 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.