---
title: "Automations"
description: "Understand Pro and Elite Automations that run Agent Y2 on a schedule or after a profile report completes."
canonical: https://y2.dev/docs/automations/
---

Automations

# Automations

Understand Pro and Elite Automations that run Agent Y2 on a schedule or after a profile report completes.

Automations run a bounded Agent Y2 instruction without requiring someone to open Chat. An Automation runs on a schedule or after a selected profile finishes a report. Its output can stay inside a Project.

Pro and Elite only

Automations are not included with Free or Lite. Pro workspaces can keep up to 10 active, paused, or draft definitions. Elite workspaces can keep up to 100. The limit is shared by the workspace.

## Definition and run separation

The Automation definition stores its name, instruction, trigger, notification policy, optional Project, and current revision. Every execution creates a separate run snapshot. Editing a definition does not rewrite prior run history.

Only one run for a definition can execute at a time. When a trigger arrives while another run is active, the newer run is skipped instead of overlapping.

## Trigger types

| Trigger                  | Behavior                                                                       |
| ------------------------ | ------------------------------------------------------------------------------ |
| Schedule                 | Daily, weekly, or monthly in the selected IANA timezone.                       |
| Profile report completed | Runs once for each accepted completion event from the selected active profile. |
| Manual                   | **Run now** creates an immediate run from an active definition.                |

Profile triggers must reference a profile owned by the same user in the same workspace. A Project-bound Automation needs an active Project in the same workspace and write access for the Automation owner.

## Access changes and downgrade safety

Y2 checks current workspace membership, plan access, definition revision, and Project access again when a run starts. If Automations are no longer available, Y2 skips the run, pauses the definition, and cancels its schedule. A downgraded owner can still pause or archive an existing definition so cleanup is not blocked by the upgrade gate.

## Cost and output

Each accepted run reserves an Agent Y2 budget. It settles actual model and tool costs or releases unused funding after failure or cancellation. Output is written to the definition's workspace-bound thread. Project-bound output stays in that Project.

## Elite governance

Elite audit logs bind Automation creation, edits, status changes, and manual run requests to the acting user and workspace. Run records also retain the owner, workspace, trigger, definition revision, billing state, and output identifiers.

## Choose the next task

[Create an Automation](https://y2.dev/docs/automations/creating): Configure a trigger, instruction, Project, and notification policy.

[Automations reference](https://y2.dev/docs/automations/reference): Review limits, statuses, triggers, run states, and access checks.

[Use Projects](https://y2.dev/docs/projects): Build the private objective and context an Automation can operate within.