Weekly Strava training recap in Notion

Build me an agent workflow that writes a weekly training recap to my Notion training journal every Sunday evening.

Trigger: cron, every Sunday at 7pm local time. (Strava is not in pollProviders, so cron is the right choice.)

At setup, ask me for: the Notion database ID of my training journal, the IANA timezone for the schedule, and optional sport filters (for example running, cycling, swimming) to scope which activities are included.

When it runs, the agent should:

1) Call Strava List Athlete Activities for the last 7 days (use the after/before timestamps for the most recent Mon to Sun window in my timezone), paginating until all activities are retrieved. Apply the configured sport filters if any.

2) Call Strava Get Athlete Stats to get recent totals and year to date totals for context.

3) Compute the narrative recap: total volume by sport (distance, moving time, elevation), longest single session, hardest effort (use suffer score / relative effort if present, else heart rate or pace), week over week trend versus the prior 7 days, and a rough recovery balance read (e.g. high volume back to back days, or balanced distribution). Then write 2 or 3 themes or recommendations for the upcoming week.

4) Call Notion Create a Page as a child of the configured database. Title the page with the week range, for example "Training week: May 19 to May 25". Set any required database properties (date range, total distance, total time) if the database has them.

5) Call Notion Append Block Children on the new page to write the structured recap as Markdown blocks: a short opening summary, a stats table (sport, sessions, distance, moving time, elevation), headings for Longest session, Hardest effort, Week over week, Recovery balance, and Themes and recommendations for next week. Include the year to date totals at the bottom as a small footer.

If there were no activities in the window, still create the page and write a short rest week note plus the year to date totals so the journal stays continuous.

Tone: first person, coach-like, concise. No emojis. Use plain Markdown headings and a table, nothing fancy.