Weekly macro briefing in Notion

Build me a weekly US macro briefing that runs on a cron trigger every Friday at 4:30pm ET, after the cash equity close and the last weekly economic prints have landed.

Data collection. For a configurable list of YCharts indicator codes (defaults: CPI year-over-year, unemployment rate, nonfarm payrolls, 10-year Treasury yield, federal funds rate, ISM manufacturing PMI, real GDP growth, retail sales), call YCharts Get Indicator Data Points to fetch the latest reading and Get Indicator Data Series to fetch the trailing twelve months of values. Remember that YCharts indicator codes use the I: prefix, indicator endpoints do not take calculation codes (the indicator code itself is the metric), and the series response is unwrapped as results: { date, val }. Batch the indicators in a single comma-separated call where possible (up to 100 per request) and always check meta.status in the response body since YCharts can return HTTP 200 with an error envelope.

Analysis. For each indicator, compute the week-over-week change, the month-over-month change, the trailing-twelve-month range (min, max, current percentile), and a short qualitative read (accelerating, decelerating, inflecting, range-bound). Feed this structured snapshot into the agent so it can spot trends and turning points instead of restating raw numbers.

Briefing. Have the agent write a narrative weekly macro briefing organized as: (1) Headline data, the two or three most important prints of the week; (2) What changed and why it matters; (3) Where the cycle sits, growth, inflation, labor, and policy stance; (4) One or two implications for equity exposure (sector or factor tilts); (5) One or two implications for fixed income exposure (duration, credit, or curve). Tone is institutional but readable, similar to what an advisor firm or finance newsletter publishes on Friday afternoons. Keep it tight, roughly 400 to 700 words. Avoid em dashes.

Publishing. Use Notion Create a Page to publish the briefing as a new page in a configurable Notion research database. Title each page with the week-ending date in YYYY-MM-DD form so the database becomes a chronological, searchable archive. Set any database properties that exist (date, status, author) and write the briefing into the page body as Notion blocks (headings for each section, paragraphs for prose, a small table or bullet list summarizing the week's prints at the top). Send the Notion-Version header that matches the Notion common docs.

Inputs to expose in the workflow form: the YCharts indicator codes to track (with sensible defaults), the Notion database ID where briefings get filed, and an optional list of distribution channels to also notify (Slack channel, email list) so the team can extend it later. If a YCharts call fails or returns an error envelope, surface the indicator code that failed and continue with the rest rather than aborting the whole run.