> ## Documentation Index
> Fetch the complete documentation index at: https://modem.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Automations
> Run AI prompts on a schedule or after specific events
export const Prompt = ({text, variant = 'accent'}) => {
const [copied, setCopied] = useState(false);
const handleCopy = async () => {
try {
await navigator.clipboard.writeText(text);
setCopied(true);
setTimeout(() => setCopied(false), 2000);
} catch {}
};
const clipboardIcon = ;
const checkIcon = ;
const promptIcon = ;
return
{promptIcon}
{text}
;
};
**Automations** let you run the Modem Agent without opening chat. You can run a prompt on a schedule or trigger it when a specific event happens.
## How It Works
An automation is a prompt plus a run condition. In the dashboard, you choose a **Type**:
| Type | Best for | Configuration |
| ------------- | -------------------------------------------------- | ------------------------------------------------- |
| **Scheduled** | Digests, recurring checks, and one-time follow-ups | Pick **Daily**, **Interval**, or **Once** |
| **Event** | Reacting to PRs or topic changes | Pick the event that should trigger the automation |
Automations use the same agent capabilities you use in chat. Depending on what integrations you have connected and what capabilities you allow, an automation can post to Slack, send email, create Linear issues, link topics to GitHub PRs, or take other actions on your behalf.
For event automations, Modem automatically passes the event details to the agent. You do not need template variables or special placeholders in your prompt. Just describe what you want done in plain language.
Slack messages can be sent to any user in your connected workspace. Emails can only be sent to members of your Modem organization.
## Automation Types
### Scheduled automations
Use scheduled automations when you want a recurring or one-time run.
### Event automations
Use event automations when you want Modem to react as soon as something happens.
Supported events today:
* **GitHub PR Created**
* **GitHub PR Merged**
* **Topic Created**
* **Topic Priority High**
## Creating an Automation
The easiest way to create an automation is to ask the agent:
The agent will set up the automation for you, including the prompt and the automation type.
### Creating an automation (manually)
Go to **Automations** in your dashboard.
Click **New Automation**. Give it a name and write the prompt you want the agent to execute.
Pick **Scheduled** or **Event**.
If you chose **Scheduled**, pick:
* **Daily** for runs on selected days at a specific time
* **Interval** for repeating runs every 30 minutes to 24 hours
* **Once** for a single future run
If you chose **Event**, select the event that should trigger the automation.
Leave capabilities on **all** to let the automation use every available tool, or switch to a custom subset if you want a narrower action surface.
Save the automation. Scheduled automations run at the configured time. Event automations run when the selected event occurs.
## Managing Automations
The automations list shows each automation's type, enabled status, recent runs, and last updated time. Scheduled automations show when they run. Event automations show the event they listen for.
On an automation's detail page, scheduled automations also show the **Next Run** time. Event automations do not, because they only run when the selected event happens.
You can:
* **Pause and resume** an automation without deleting it
* **Run now** to trigger an immediate execution
* **Edit** the prompt, type, or capabilities
* **View run history** to see past executions, their results, and any errors
## Related
The same AI that powers automation execution.
Use PR activity as an automation trigger.
Trigger automations when new topics appear or reach high priority.