> 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/get-alerted-when-a-person-appears-in-footage.md).

# Get alerted when a person appears in footage

Get an email whenever Shade recognizes a specific person in new photos or video.

**Outcome:** whenever Shade recognizes a person you choose (a player, a spokesperson, or talent with usage restrictions) in newly indexed media, you get an email with the file, and the file is added to that person's collection.

**Who it's for:** sports, newsroom, and brand teams that need to know quickly when specific people show up in incoming media.

**Time:** about 15 minutes, plus a few minutes to set up each person's profile.

## Before you start

* Build [Your first automation](/guides/automations/your-first-automation.md) first if you haven't used the automation editor.
* Create a profile for the person in **People**, with two or three clear sample photos. See [Facial Recognition](https://academy.shade.inc/ai-tools/facial-recognition).
* Make sure incoming media lands in folders that aren't excluded from AI. Excluded folders aren't scanned for faces.

## Steps

{% stepper %}
{% step %}

### Trigger on the person

Create an automation named `Alert: Jordan appears`. Choose **Person Recognized** and set **Person** to the profile. Leave **Person** empty to run for anyone who has a profile.
{% endstep %}

{% step %}

### Collect the files

Add **Add to Collection** with a collection such as **Jordan: new appearances**, and set **Asset** to the asset from the trigger.
{% endstep %}

{% step %}

### Send the alert

Add **Send Email**:

* **To:** the person who needs to know
* **Subject:** the person's name followed by `appeared in new media`
* **Body:** the asset's name and path from the trigger
  {% endstep %}

{% step %}

### Save, activate, and test

Click **Save**, then **Activate**. Upload a photo of the person to an AI-indexed folder. Recognition runs after indexing, so allow a few minutes.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Face recognition is per drive. Build this automation in each drive where you need the alert, with a profile for the person in that drive.
{% endhint %}

## Variations

* **Talent with usage limits:** instead of emailing, set a **Rights** metadata field to **Restricted** with **Update Asset Metadata**, so nobody uses the shot by accident.
* **Fewer emails:** add a **Filter** so the alert only fires for files uploaded to a specific folder, such as `Incoming/Press`.

## Related guides

* [Build a searchable archive](/guides/search-ai-and-archives/build-a-searchable-archive.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/get-alerted-when-a-person-appears-in-footage.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.