> 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/auto-curated-workflow.md).
# Auto-Curated Workflow
Once an Auto-Curated newsletter has been configured and enabled, Feedotter automatically creates, populates, and prepares newsletter issues according to your settings.
### Auto-Curated Workflow Overview
Every Auto-Curated issue follows the same basic workflow:
**Schedule → Issue Created → Content Preloaded → Notification Sent → Review Window → Published**
Depending on your settings, editors may review and publish the issue manually, or Feedotter may automatically publish it after a configured delay.
### 📅 Step 1: Scheduled Issue Creation
At the scheduled date and time configured in **Newsletter Default Settings → Scheduling**, Feedotter automatically creates a new newsletter issue.
The issue is created using the newsletter's template and default settings.
The newly created issue appears in the newsletter's issue list and is immediately available for review and editing.
#### What determines when an issue is created?
Issue creation is controlled by:
* Frequency
* Days of the week
* Scheduled time
* Timezone
* Automation Status
If Automation Status is enabled, Feedotter will create new issues according to the configured schedule.
### 📰 Step 2: Content Preloading
After the issue is created, Feedotter automatically populates newsletter sections using the content sources configured in **Newsletter Default Settings → Content**.
Each section is processed independently.
For example:
| Section | Content Source | Posts Loaded |
| ----------- | ----------------- | ------------ |
| Lead Story | Company News Feed | 1 |
| Top Stories | Company News Feed | 3 |
| Podcast | Podcast Feed | 1 |
Any section configured as **Off** remains empty and can be populated manually by editors.
#### Where does the content come from?
Content is pulled from the content sources assigned to each newsletter section.
Feedotter uses the latest available content from those sources at the time the issue is created.
### 🔔 Step 3: Notification Sent
Once the issue has been created and populated, Feedotter sends a notification email to the newsletter's configured notification recipients.
Notification recipients are configured in:
**Newsletter Default Settings → Basics**
Up to three email addresses can be configured for each newsletter.
These recipients are notified whenever a new Auto-Curated issue is created and ready for review.
### ⏳ Step 4: Review Window
After the issue is created, editors have an opportunity to review the newsletter before it is published.
During this review period, editors can:
* Review content
* Add or remove articles
* Reorder content
* Update text and images
* Save changes
* Publish immediately
* Cancel a scheduled publication
The length of the review window depends on the **Delay Before Publishing** setting.
For example:
* Issue created: 8:00 AM
* Delay before publishing: 15 minutes
* Scheduled publish time: 8:15 AM
Editors have 15 minutes to review and make changes before publication occurs.
#### Managing a Scheduled Publication
If automatic publishing is enabled, a notification banner appears at the top right of the issue editing screen while it is waiting to be published.
From this banner, editors can:
* **Publish Now** to immediately publish the issue to the connected ESP.
* **Cancel** to stop the scheduled publication and return the issue to draft status.
This allows editors to make last-minute decisions during the review window without changing the newsletter's default automation settings.
> **Note:** Canceling a scheduled publication only affects the current issue. Future Auto-Curated issues will continue to follow the newsletter's configured automation settings.
### 🚀 Step 5: Publication
The final step depends on whether automatic publishing is enabled.
#### If Automatic Publishing Is Enabled
Feedotter automatically publishes the issue to the connected ESP after the configured delay period expires.
No additional action is required.
#### If Automatic Publishing Is Disabled
The issue remains in draft status until an editor manually publishes it.
This allows teams to maintain complete editorial control over when newsletters are sent.
### Have more questions? Read the FAQ.
{% content-ref url="/pages/TyPeszuvZRVBLkQj4B32" %}
[Auto-Curated FAQ](/newsletters/auto-curated/auto-curated-faq.md)
{% endcontent-ref %}
---
# 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/auto-curated-workflow.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.