# Automation Studio

## Package docs status

This page is generated from public package documentation in `capell-4/packages` and the package manifest checked into the source repository.

| Field | Value |
| --- | --- |
| Composer package | `capell-app/automation-studio` |
| Package slug | `automation-studio` |
| Product group | Capell Automation |
| Tier | premium |
| Bundle | `automation` |
| Runtime contexts | `admin`, `console` |
| Capell version | `^4.0` |
| Source repository | `capell-app/packages` |
| Source path | `packages/automation-studio` |
| Docs source | `packages/automation-studio/docs` |
| Manifest | [`capell.json`](https://github.com/capell-app/packages/edit/4.x/packages/automation-studio/capell.json) |

Automation Studio is the rule orchestration layer for Capell package events.

This first package slice is intentionally database-free. Packages or future admin resources can register `AutomationRuleData` objects against the package-local `AutomationRuleRegistry`, and Automation Studio will dispatch matching trigger events to registered action handlers.

## Current foundation

- Triggers: form submitted, access approved, page published, campaign converted.
- Actions: send email, webhook, tag contact, create note, subscribe user, queue agent capability, run Public Action.
- Built-in handler: `public_action`, which delegates to Public Actions when that package is available.
- Package-local listeners normalize optional package events without editing those packages.

See `docs/automation-studio.md` for the implementation plan and next slices.