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

# Set up Autopilot

> Pick what Autopilot does, connect your website repository and Slack, and start the first run in a few minutes.

Setup takes three steps and ends with a first run. You need to be a workspace owner or admin.

## Before you start

Autopilot works from the data Notra already has, so each connection gives more automations something to act on.

| What | Why Autopilot needs it | Without it |
| - | - | - |
| **GitHub** with your website repository | Every post and fix is a pull request there | Setup can't finish. Connect the [GitHub integration](https://www.usenotra.com/docs/integrations/github.md) first. To publish to a [Notra Site](https://www.usenotra.com/docs/sites/overview.md), pick it later under **Settings → Publishing → Site** |
| **A GEO project** with tracked prompts | Content gaps, comparison pages, refreshes, landing copy, readiness and measuring results | Only **Write about releases** has something to read. See [Projects](https://www.usenotra.com/docs/geo/projects.md) |
| **A brand identity** on that project | The voice, tone, language and house rules of every post | Posts fall back to a neutral voice. See [Brand voice](https://www.usenotra.com/docs/concepts/brand-voice.md) |
| **Google Search Console** on the project | Search gaps, **Add internal links**, landing pages that rank 4 to 20 and the indexing follow-up | **Add internal links** skips and says why. The others run without search gaps, rank-based landing pages and the indexing check. See [Google Search Console](https://www.usenotra.com/docs/integrations/google-search-console.md) |
| **Slack** | The daily brief and acting on it with 👍 and 👎 | No daily brief is sent. Owners get an email for each new draft instead, while **Drafts to review** is on under **Settings → Notifications**. See [Slack](https://www.usenotra.com/docs/integrations/slack.md) |
| **AI credits** or pull request credits | Each pull request Autopilot opens is charged | Work that would open a pull request is saved as an idea or retried the next day |

> [!TIP]
>
> Run a GEO scan and an [Agent Readiness](https://www.usenotra.com/docs/geo/agent-readiness.md) scan before you turn Autopilot on, so its first run has gaps and issues to act on.

## Turn on Autopilot

**1. Open Autopilot**

Switch the sidebar to **Studio**, open **Autopilot** and press **Get started**. The first step shows what Autopilot does: it runs once a day at your time, opens draft pull requests with fixes and new posts, and sends a daily brief.

![The first step of the Autopilot setup with the Get started button and the list of automations](https://mintcdn.com/notra/VoAWbnubtjH84omr/images/autopilot/setup-light.webp?fit=max\&auto=format\&n=VoAWbnubtjH84omr\&q=85\&s=fb66919c8762ca3d9e3e10f629868bf1)

**2. Pick the automations**

All eight automations are on. Switch off the ones you don't want yet and press **Continue**. You can turn any of them on or off later from the [templates](https://www.usenotra.com/docs/autopilot/automations/overview.md). If you're unsure, see [Grow with Autopilot](https://www.usenotra.com/docs/autopilot/grow.md) for a setup per goal.

**3. Connect your repository and Slack**

Pick the **website repository**, the repository your site is built from. Autopilot opens its draft pull requests there, on the repository's default branch. Without GitHub, press **Connect GitHub** to install the Notra GitHub App first.

Under **Slack channel**, pick the channel for the daily brief or choose **Create a channel** (the default name is `notra-autopilot`). Invite the Notra app to an existing channel so it can post there. Without Slack, press **Connect Slack**, or skip it.

Under **Runs daily at**, pick the hour. Your browser's timezone is shown under it and saved with the hour.

![The Connect step with the website repository, the Slack channel and the hour Autopilot runs](https://mintcdn.com/notra/VoAWbnubtjH84omr/images/autopilot/setup-connect-light.webp?fit=max\&auto=format\&n=VoAWbnubtjH84omr\&q=85\&s=1925cc7232ab21ad27fa249d5ae461aa)

**4. Turn on Autopilot**

Press **Turn on Autopilot**. The first run starts right away ("Autopilot is checking your site now"), and the page switches to the **Automations** tab. Open the run from **Analytics → Recent runs** to watch each automation work.

## Defaults from setup

Setup picks a few defaults. Check them in [Settings](https://www.usenotra.com/docs/autopilot/settings.md) if they don't fit.

Approvals start on Auto for new posts, page updates and readiness fixes. The first pull request of each group still waits for a person to merge it. After that, Autopilot marks later pull requests of the group ready and publishes them at 09:00 on the first weekday at least 24 hours away, unless someone steps in. If you want to merge everything yourself, set the groups to **Ask**. See [Approvals](https://www.usenotra.com/docs/autopilot/review-and-publish.md#approvals).

Autopilot looks for your blog folder in places like `content/blog`, `src/content/blog`, `posts` or `_posts`, also under `apps/*` and `packages/*`. If your posts live somewhere else, set **Settings → Publishing → Blog folder**. Release posts read your five most recently pushed repositories until you pick some under **Read from**, and drafts nobody touches close after 14 days (**Settings → Housekeeping**).

Autopilot works with the GEO project that was active during setup, or the workspace's first project, and writes with that project's brand identity.

## After the first run

What the first run opens depends on your data. If the readiness scan found something your repository can fix, expect a readiness fix. If a content gap has enough evidence, expect a post or an idea. Autopilot keeps at most three of its pull requests open at a time, and an automation that did nothing says why in the run log.

> [card] [Review the first pull request](https://www.usenotra.com/docs/autopilot/review-and-publish.md)
>
> Read the post, ask for changes and merge it.

> [card] [Read the daily brief](https://www.usenotra.com/docs/autopilot/daily-brief.md)
>
> What the brief contains and how to act on it.

> [card] [How a run works](https://www.usenotra.com/docs/autopilot/how-it-works.md)
>
> Why Autopilot opened what it opened, and what it waits for.

> [card] [Troubleshooting](https://www.usenotra.com/docs/autopilot/troubleshooting.md)
>
> The run opened nothing, or the brief didn't arrive.


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