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

# Automation

> Ask Twill to set up recurring automations that act on your connected integrations

Many operational developer tasks are repetitive but still require context and judgment—triaging issues, investigating alerts, reviewing dependency updates, syncing work across tools. Instead of configuring these workflows yourself, you describe what you want and Twill sets it up.

<Frame>
  <img src="https://mintcdn.com/twill/kGLDvgTksG_NxLEU/images/automations-list.png?fit=max&auto=format&n=kGLDvgTksG_NxLEU&q=85&s=655cd32700f0536ca99b3b83ced62771" alt="Twill automations dashboard showing scheduled automation templates" width="2880" height="1800" data-path="images/automations-list.png" />
</Frame>

## How It Works

Ask the agent to create an automation in plain language. Twill verifies that the required integrations are connected, sets up the schedule, and writes the instructions for the recurring job. On each run, an orchestrator agent gathers context from your connected integrations (GitHub, Linear, Slack, Notion, Sentry, GCP, AWS), decides what work needs doing, and spawns coding tasks or reports back.

You can set up automations from any surface where you interact with Twill—the web app, Slack, or the API.

<Info>
  Twill checks that each integration the automation depends on is actually
  connected before creating it. If something is missing, it tells you what to
  connect first.
</Info>

## Connected Integrations

Automations can read from and act on any integration connected to your workspace:

| Integration      | What automations can access                              |
| ---------------- | -------------------------------------------------------- |
| **GitHub**       | Issues, PRs, CI status, review comments, repository data |
| **Linear**       | Issues, projects, sprint status, labels                  |
| **Slack**        | Channel messages, threads, alerts                        |
| **Notion**       | Pages, databases, comments                               |
| **Sentry**       | Error events, issue details, stack traces                |
| **Google Cloud** | Cloud Run logs, service status                           |
| **AWS**          | Read-only access to cloud resources                      |

Connect integrations in **Settings → Integrations**. Automations can combine data from multiple integrations in a single run.

***

## Examples

### Issue Triage

**Ask:** "Set up a daily automation to triage open GitHub issues—prioritize bugs, label them, and spawn fix tasks for critical ones."

Twill reads open issues each morning, categorizes them by severity, and creates coding tasks for bugs that have enough context to act on.

***

### Dependency Updates

**Ask:** "Create a weekly automation to check for outdated dependencies, update them, run tests, and open PRs."

Twill checks your dependency files, identifies available updates, tests them in a sandbox, and opens PRs for the ones that pass.

***

### Linear Sprint Pickup

**Ask:** "Every weekday morning, pick up ready Linear issues labeled for this repo and start working on them."

Twill reads your Linear board, finds issues marked as ready, and spawns implementation tasks for each one.

***

### Error Monitoring

**Ask:** "Monitor Sentry for new error spikes and investigate the top ones daily."

Twill pulls recent error events from Sentry, identifies patterns, and either proposes fixes or reports what it found.

***

### Stale PR Cleanup

**Ask:** "Once a week, go through open PRs that have unresolved review comments or merge conflicts and address them."

Twill reads PR review threads, applies requested changes, resolves merge conflicts, and pushes updates.

***

### Notion Roadmap to Code

**Ask:** "Every Monday, read the feature specs from our Notion roadmap database and spawn implementation tasks for anything marked as ready."

Twill reads your Notion database, picks up specs that are ready for development, and creates coding tasks with the full context from the Notion page.

***

## Managing Automations

Once created, automations appear in the **Automations** dashboard where you can:

* **Toggle** on/off with the switch
* **Force trigger** for immediate execution
* **Edit** instructions or schedule
* **Delete** when no longer needed

You can also ask the agent to update, pause, resume, or delete automations conversationally.

## Schedules

Automations run on cron schedules. When setting one up, you can describe the schedule naturally ("every weekday at 9 AM", "once a week on Monday mornings") and Twill configures the cron expression. See [Cron Triggers](/triggers/cron) for details on schedule options and templates.