> 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/guides-zh/zi-dong-hua/dang-hua-mian-zhong-chu-xian-mou-ge-ren-shi-shou-dao-ti-xing.md).

# 当画面中出现某个人时收到提醒

每当 Shade 在新照片或视频中识别出特定人物时，都会向你发送电子邮件。

**结果：** 每当 Shade 在新编入索引的媒体中识别到你选择的人物（球员、发言人或有使用限制的艺人）时，你都会收到一封附带该文件的电子邮件，该文件也会被添加到该人物的集合中。

**适用对象：** 需要在传入媒体中尽快知道特定人物何时出现的体育、新闻编辑室和品牌团队。

**时间：** 大约 15 分钟，再加上为每个人物设置资料所需的几分钟。

## 开始之前

* 创建 [你的第一个自动化](/guides/guides-zh/zi-dong-hua/ni-de-di-yi-ge-zi-dong-hua.md) 如果你还没有使用过自动化编辑器，请先进行此操作。
* 为该人物在 **人员**中创建一个资料，并提供两到三张清晰的示例照片。参见 [人脸识别](https://academy.shade.inc/ai-tools/facial-recognition).
* 确保传入媒体存放在未被 AI 排除的文件夹中。被排除的文件夹不会进行人脸扫描。

## 步骤

{% stepper %}
{% step %}

### 以该人物为触发条件

创建一个名为 `警报：Jordan 出现了`。选择 **识别到人物** 并将 **人物** 设置为该资料。将 **人物** 留空则对任何拥有资料的人运行。
{% endstep %}

{% step %}

### 收集文件

添加 **添加到集合** 并使用如下集合，例如 **Jordan：新出现**，并将 **资源** 设置为触发器中的资源。
{% endstep %}

{% step %}

### 发送警报

添加 **发送电子邮件**:

* **收件人：** 需要知晓的人
* **主题：** 该人物姓名后接 `出现在新媒体中`
* **正文：** 来自触发器的资源名称和路径
  {% endstep %}

{% step %}

### 保存、激活并测试

点击 **保存**，然后 **激活**将该人物的照片上传到一个由 AI 编索引的文件夹。识别会在索引完成后运行，因此请等待几分钟。
{% endstep %}
{% endstepper %}

{% hint style="info" %}
人脸识别按驱动器分别进行。请在每个需要接收警报的驱动器中创建此自动化，并在该驱动器中为该人物建立资料。
{% endhint %}

## 变体

* **有使用限制的艺人：** 不发送电子邮件，而是将一个 **权限** 元数据字段设置为 **受限** 使用 **更新资源元数据**，以免有人误用该镜头。
* **更少的电子邮件：** 添加一个 **筛选器** 这样警报只会在文件上传到特定文件夹时触发，例如 `Incoming/Press`.

## 相关指南

* [构建可搜索的存档](/guides/guides-zh/sou-suo-ai-he-dang-an/gou-jian-ke-sou-suo-de-gui-dang.md)
* [你的第一个自动化](/guides/guides-zh/zi-dong-hua/ni-de-di-yi-ge-zi-dong-hua.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 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/guides-zh/zi-dong-hua/dang-hua-mian-zhong-chu-xian-mou-ge-ren-shi-shou-dao-ti-xing.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.