> For the complete documentation index, see [llms.txt](https://docs.feedotter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedotter.com/newsletters/auto-curated/setting-up-an-auto-curated-newsletter.md).
# Setting Up an Auto-Curated Newsletter
### Before You Begin
Before enabling Auto-Curated newsletters:
* A newsletter template must already exist
* Content sources must already be configured
* Newsletter sections must be available in the template
* An ESP integration must be connected if you plan to enable automatic publishing
> Note: Section availability is typically configured during the newsletter template setup process by our team.
{% hint style="info" icon="bell-exclamation" %}
**Important:** Auto-Curated settings are configured on a **per-newsletter basis**. Each newsletter can have its own content sources, notification recipients, creation schedule, publishing settings, and review window. Changes made to one newsletter will not affect any other newsletters in your account.
{% endhint %}
### Configure Content Preloading
Content preloading determines what content Feedotter automatically adds to each newsletter issue when it is created.
Each newsletter section can be assigned a content source and configured to automatically pull a specific number of posts. This allows Feedotter to build a draft newsletter using your existing content sources.
For example, you may choose to automatically populate:
* 1 article in a Lead Story section
* 3 articles in a Top Stories section
* 1 podcast episode in a Podcast section
Sections can also be left unconfigured if you prefer to curate them manually.
#### How to configure content preloading:
1. Navigate to **Newsletter Default Settings → Content:**
1. Locate the section you would like to automate. These will be labeled according to the sections in your template.
2. Select a content source from the dropdown menu.
3. Choose the number of posts Feedotter should automatically load into the section.
4. Repeat for any additional sections.
5. Leave a section set to **Off** if it should remain manually curated.
**Here's an example:**
When a new issue is created, Feedotter will automatically pull the latest content from the selected sources and populate the configured sections.
> Tip: Start by automating your most repetitive sections first. You can always leave high-touch editorial sections manually curated.
### Configure Scheduling
Scheduling controls when Feedotter automatically creates new newsletter issues.
When scheduling is enabled, Feedotter will create issues according to the frequency, days, time, and timezone you specify.
#### How to configure scheduling:
1. Navigate to **Newsletter Default Settings → Scheduling**.
1. Select a **Frequency**.
2. Select the day or days on which issues should be created.
3. Choose the creation time.
4. Select the appropriate timezone.
5. Click **Activate.**
6. The automation status will defualt to on. This controls whether the automation is running or not:
From here, Feedotter will automatically create new issues according to the configured schedule.
{% hint style="info" %}
The issue creation schedule determines when Feedotter generates a new issue, not when the newsletter is published. Read below to learn how to configure automatic publishing with a delay window if desired.
{% endhint %}
### Configure Automatic Publishing
Automatic Publishing allows Feedotter to publish an Auto-Curated issue to your connected Email Service Provider (ESP) after it has been created.
This option is ideal for teams that want a review period before publication while still reducing manual publishing steps.
#### How to enable ESP Publishing:
1. Navigate to **Newsletter Default Settings → Scheduling**.
2. Enable **Publish draft to ESP after creation** (ensure the box is check):
1. Enter the number of minutes Feedotter should wait before publishing.
2. Click **Save**.
#### Understanding the Review Window
The delay period creates a review window between issue creation and publication.
During this time, editors can:
* Review the generated issue
* Make content changes
* Save updates
* Publish immediately
* Cancel the scheduled publication
If no action is taken, Feedotter will automatically publish the issue to the connected ESP once the delay period expires.
For example, if an issue is created at 8:00 AM and the delay is set to 15 minutes, Feedotter will automatically publish the issue at 8:15 AM unless an editor intervenes.
### Setup Complete — What Happens Next?
Your Auto-Curated newsletter is now configured.
When the scheduled time arrives, Feedotter will automatically create a new issue, preload content into your configured sections, notify editors, and optionally schedule the issue for publication.
The exact sequence depends on your automation settings.
➡️ Continue to [**Auto-Curated Workflow** ](/newsletters/auto-curated/auto-curated-workflow.md)to learn:
* When issues are created
* When editors are notified
* How the review window works
* When publication occurs
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.feedotter.com/newsletters/auto-curated/setting-up-an-auto-curated-newsletter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.