> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/getting-started/learning/stackai-building-challenges/2.-email-a-news-report.md).

# 2. Email a News Report

## Challenge overview

Build an automated news report that runs every Monday, Wednesday, and Friday.

The report must stay short, polished, and consistent. It must only use approved sources.

### Scenario

> We want an automated news report that gets sent to us every Monday, Wednesday, Friday. The report should be short and sweet, but quality is key. It must have two sections:
>
> 1. World News (Politics)
> 2. Legal News
>
> Each section must only research what’s published on our trusted websites (no other sources allowed). The report should be very polished and visually consistent with our newsletter style (see example).

### Scenario

> We want an automated news report that gets sent to us every Monday, Wednesday, Friday.
>
> The report should be short and sweet, but quality is key.
>
> It must have two sections:
>
> 1. World News (Politics)
> 2. Legal News
>
> Each section must only research what’s published on our trusted websites (no other sources allowed).
>
> The report should be very polished and visually consistent with our newsletter style (see example).

The report must include these sections:

1. World News (Politics)
2. Legal News

### Approved sources

#### World News

* Reuters
* Associated Press (AP)
* BBC News
* Financial Times
* The Economist
* The Wall Street Journal

#### Legal News

* Law360
* National Law Review
* ABA Journal
* Just Security

### Formatting reference

Use this file as the design reference for the final report.

{% file src="/files/jEupbc8E5myyCuLVzBCa" %}

#### What to match

{% hint style="info" %}

* Visual hierarchy between the title and section headers
* Consistent spacing between sections
* Clean link styling and readable bullet lists
  {% endhint %}

### What to build

Your workflow should:

1. Run on Monday, Wednesday, and Friday.
2. Check each approved website on every run.
3. Collect only relevant items for the two required sections.
4. Exclude unapproved sources.
5. Format the final output in a consistent newsletter style.
6. Send the report by email.

### Key considerations

{% hint style="info" %}

* Prevent the agent from filling gaps with unapproved sources.
* Make coverage deterministic across all ten approved sites.
* Keep typography, spacing, section headers, bullet style, and link formatting consistent.
* Use **Web Search** when search results are enough.
* Use browser-based tools when page interaction or fixed page rendering is required.
* Keep the design easy to update when the approved site list changes.
  {% endhint %}

### Extension

Add a logo and a header image to every report.

### Helpful docs

* [Web Search](/workflow-builder/apps/web-search.md)
* [Template Node](/workflow-builder/outputs/template-node.md)
* [DocRaptor](/workflow-builder/apps/docraptor.md)
* [Outlook](/workflow-builder/apps/outlook.md)
* [StackAI](/workflow-builder/core-nodes/stackai.md)


---

# 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.stackai.com/getting-started/learning/stackai-building-challenges/2.-email-a-news-report.md?ask=<question>&goal=<endgoal>
```

`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.