← All use cases

中文

Automation & agents · Claude Cowork

Turn yesterday's newsletters into a morning briefing document

Idea + starter prompt, not run by us yet

For: People who subscribe to many newsletters and never get through them

The author forwards newsletters to Readwise. Cowork cannot reach the internet, so an n8n workflow acted as an MCP bridge to the Readwise API. Through it, Cowork pulled the previous day's articles and produced a two-page Word briefing with a short summary at the top. The MP3 step failed. Without a proper cloud voice, the audio sounded robotic.

Steps

  1. Forward your newsletters to a read-later service that has an API, such as Readwise.
  2. If your agent cannot reach the internet, give it a bridge such as an n8n workflow exposed as an MCP server.
  3. Ask for a two-page briefing with a short executive summary and links to the originals.
  4. Do not expect good audio from a sandboxed agent. Claude Code can call a cloud voice service instead.
  5. Read the briefing against two or three originals to check it did not invent anything.

Starter prompt

Starter prompt. Change the [brackets] first.

Trial first: use only [3] saved articles and write the briefing to [trial-briefing.docx]. If you cannot reach the service, say so and stop. Do not guess.

This job only reads and drafts, and it changes nothing outside [output folder]. After my yes, use the articles I saved yesterday in [read-later service] and write a two-page morning briefing: a five-sentence executive summary, then one short paragraph per article with a link to the original.

Do not add facts that are not in the articles. Save the result as a document and show it to me. Stop and wait for my yes before you email it, share it or turn it into audio. Showing me the briefing is not permission. I will not paste any API keys here.

Original post: ishyshkova.substack.com · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.