# Automations

Event to action. An automation is a trigger and a graph: something happens,
and a run walks the steps for the subscriber it happened to, sending,
waiting, moving tags and branching on a condition. Needs `sending`, because
what an automation decides is that the list will receive something.

Every event Commune publishes is a trigger. `GET /automation-triggers` says
which are about a subscriber and what each one's events carry, which is what
a condition can ask about.

Nothing an automation holds reaches anybody until it is turned on, which is
one operation of its own with every gate behind it.


## Operations

- [List a newsletter's automations](https://api-reference.usecommune.dev/operation/operation-listnewsletterautomations.md)

- [Create an automation](https://api-reference.usecommune.dev/operation/operation-createautomation.md)

- [List the events an automation can trigger on](https://api-reference.usecommune.dev/operation/operation-listautomationtriggers.md)

- [Retrieve an automation](https://api-reference.usecommune.dev/operation/operation-getautomation.md)

- [Archive an automation](https://api-reference.usecommune.dev/operation/operation-deleteautomation.md)

- [Update an automation](https://api-reference.usecommune.dev/operation/operation-updateautomation.md)

- [Turn an automation on](https://api-reference.usecommune.dev/operation/operation-activateautomation.md)

- [Turn an automation off](https://api-reference.usecommune.dev/operation/operation-pauseautomation.md)

- [List an automation's runs](https://api-reference.usecommune.dev/operation/operation-listautomationruns.md)

- [Send a test copy of one step's email](https://api-reference.usecommune.dev/operation/operation-sendautomationsteptest.md)

- [Retrieve an automation run](https://api-reference.usecommune.dev/operation/operation-getautomationrun.md)


[Powered by Bump.sh](https://bump.sh)