> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations

> Run an agent on a schedule: status reports, on-call handoffs, noise reviews.

Automations run Ordyn on a schedule with instructions you write. Common uses:

* A morning summary of what fired overnight and what is still open.
* An on-call handoff at the end of each rotation.
* A weekly review of which monitors are noisiest and why.

## Create an automation

From **Automations**, workspace admins can create one with:

| Field | Notes |
| - | - |
| **Title** | Used as the heading of the delivered result. Leave empty to auto-generate. |
| **Source channel** | Optional. Scope the run to one Slack channel, or leave empty to span every source: Slack, Linear, Jira, Asana, and GitHub. |
| **Delivery** | A Slack channel, email recipients, or both. |
| **Schedule** | A cron expression in your timezone, for example `0 9 * * 1` for Mondays at 9am. |
| **Instructions** | What the agent should do each run, in plain language. |

## Create one from Slack

You can also ask Ordyn in Slack to set one up, change it, run it now, or delete it. Ordyn confirms before deleting or replacing an automation's instructions.

```text theme={null}
@Ordyn every Monday at 9am, post a summary of last week's alerts to #eng-oncall
@Ordyn move the weekly noise review to Fridays
```

## Runs

Each automation keeps a history of runs with links to what it delivered. You can run one immediately to test it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.