> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deployment/monitoring-and-analytics/vision-events/automations.md).

# Automations

Send images from matching Vision Events into a project, or email an alert, automatically.

An Automation watches a Use Case and acts on every new event that matches your conditions. Use it to keep sending production images into a project without picking them by hand each time, or to get an email when an event happens. It can also email you when events stop arriving (see [No-Events Alerts](https://docs.roboflow.com/deployment/monitoring-and-analytics/vision-events/no-events-alerts.md)). To add images once, see [Add Images for Training](https://docs.roboflow.com/deployment/monitoring-and-analytics/vision-events/add-images-for-training.md).

You need the "manage\_vision\_events" permission to create or edit an Automation.

## Create an Automation

1. Open Vision Events, select a Use Case, then open the "Automations" tab.
2. If the Use Case has no Automations yet, choose "Operator feedback preset" or "Custom automation". Otherwise, click "New Automation".
3. Name the Automation and add conditions. An event must match all of them. To match one set of conditions or another, click "OR" to add a row.
4. Choose an action, then the project it sends images to or the people it emails.
5. Set the daily cap, then save.

The "Operator feedback preset" starts with conditions that match events an operator marked incorrect or inconclusive. See [Operator Feedback](https://docs.roboflow.com/deployment/monitoring-and-analytics/vision-events/operator-feedback.md).

Conditions match on event type, event field, custom metadata, device, stream, workflow, or external ID, with the same operators as the search filters. See [Query Events](https://docs.roboflow.com/deployment/monitoring-and-analytics/vision-events/query-events.md).

The daily cap limits how many images or emails one Automation can send per day. It is 1000 images by default for project actions, and 50 emails by default (1000 at most) for email alerts.

## Actions

<table data-search="false"><thead><tr><th width="290">Action</th><th>What it does</th></tr></thead><tbody><tr><td>Add to Active Learning queue</td><td>Sends matching images to the project's Active Learning review queue. The project needs a configured model.</td></tr><tr><td>Add to project as unannotated</td><td>Adds matching images to the project as unannotated images. No model or review queue is needed.</td></tr><tr><td>Send an email alert</td><td>Sends one email per matching event, right away, to the recipients you pick.</td></tr></tbody></table>

## Email Alerts

Each email shows the event image, the event fields (ex: result: fail), device, stream, workflow, external ID, and custom metadata, plus a link to the event in Vision Events. Clear "Include the event image" to send text only.

You can pick up to 10 recipients. Each must be a workspace member with the "view\_vision\_events" permission. If a recipient loses access, they stop getting emails and the "Automations" tab shows a warning on that Automation.

## No-Events Alerts

A No-Events Alert emails you when a Use Case stops getting events (ex: a camera goes offline). Set "Trigger" to "No events arrive", or pick "No-events alert" when the Use Case has no Automations yet. See [No-Events Alerts](https://docs.roboflow.com/deployment/monitoring-and-analytics/vision-events/no-events-alerts.md) for setup, timing, the email, and limits.

## Track and Manage Automations

The "Automations" tab lists each Automation with its conditions, action, and how many images or emails it sent today. Turn one off to pause it without deleting it.

"Recent activity" below the list shows each run with its event type, action, status, and image count. Email runs also show the number of recipients and an "Emailed" or "Email failed" status. "Cap reached" marks the run that used up the daily cap. Runs are kept for 90 days.

Creating, editing, and deleting an Automation is written to the workspace audit log.
