> 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/tell-a-client-their-files-are-ready.md).

# Tell a client their files are ready

Right-click a folder, type the client's email, and Shade creates a share link and sends it for you.

**Outcome:** when a delivery folder is ready, you right-click it, choose **Run automation**, and enter the client's email. Shade creates a download link for that folder and emails it to the client.

**Who it's for:** producers and editors who send "your files are ready" emails by hand every week.

**Time:** about 15 minutes.

## Before you start

* Build [Your first automation](/guides/automations/your-first-automation.md) first if you haven't used the automation editor.
* Check that link sharing is turned on for the workspace in **Settings > Sharing**. If an admin has turned off **Enable link sharing**, Shade can't create the link.

## How it works

```mermaid
flowchart LR
  T["Manual Trigger on a folder, asks for client email"] --> L["Generate Folder Share Link"]
  L --> E["Send Email with the link"]
```

A manual trigger is the right choice here, because "ready to send" is a decision a person makes. If you started this from an upload or a collection change, the client would get an email for every file.

## Steps

{% stepper %}
{% step %}

### Create a manual automation for folders

Create a new automation named `Send delivery to client`. Choose **Manual Trigger**.

* **Runs on:** **Folders**.
* **Form fields:** add a **Text** field labeled `Client email` and mark it required. Optionally add a **Long text** field labeled `Note`.

The form fields are what Shade asks for each time someone runs the automation.
{% endstep %}

{% step %}

### Create the share link

Add **Generate Folder Share Link**:

* **Path:** type `{` and choose the selected folder's path from the trigger.
* **Role:** a download role, so the client can view and download but not edit.
* **Password:** optional. If you set one, send it to the client separately, not in the same email.
  {% endstep %}

{% step %}

### Send the email

Add **Send Email**:

* **To:** the `Client email` form field from the trigger.
* **Subject:** for example `Your files are ready:` followed by the folder name from the trigger.
* **Body:** a short message with the share link's **url** from the previous step, and the `Note` field if you added one. The body supports basic HTML, such as `<p>`, `<a>`, and `<strong>`.
  {% endstep %}

{% step %}

### Save and activate

Click **Save**, then **Activate**. Manual automations only appear in menus once they're active.
{% endstep %}

{% step %}

### Run it

Right-click the delivery folder, choose **Run automation**, and pick `Send delivery to client`. Enter your own email the first time to see exactly what the client will get.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Every run creates a new link. You can see, edit, or disable each one later under **Shared Links** in the drive's sidebar, for example to add an expiry date or a view limit. See [Published Links](https://academy.shade.inc/sharing-and-collaboration/published-links).
{% endhint %}

## Variations

* **Run it from a status change instead:** use **Asset Updated** with a specific field and value, such as **Status** changing to **Approved**, with **Generate Share Link** and **Send Email**. This sends one email per file, so it suits single deliverables better than folders.
* **Two-stage approval:** when **Status** becomes **In review**, email the internal reviewer. When it becomes **Approved**, email the client. That's two automations, each triggered by a different value.
* **Deliver a collection:** to send a curated selection instead of a folder, use **Generate Collection Share Link**. See [Deliver final files to a client](/guides/review-and-client-delivery/deliver-final-files-to-a-client.md).

## Related guides

* [The client review loop](/guides/review-and-client-delivery/the-client-review-loop.md)
* [Deliver final files to a client](/guides/review-and-client-delivery/deliver-final-files-to-a-client.md)
* [Your first automation](/guides/automations/your-first-automation.md)


---

# 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/tell-a-client-their-files-are-ready.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.