Weekly Tally feedback digest to Slack and Notion

Every Monday at 9am in my local timezone, run an agent that produces a weekly insights digest from my Tally form responses and delivers it to both Slack and Notion.

Inputs the user configures: a list of Tally form IDs to include in the digest, the Slack channel ID where the digest should be posted, and the Notion database ID for the Weekly Feedback Digest archive.

What the agent should do each Monday:

1. For each configured Tally form ID, use the Tally List Submissions action to pull every submission whose creation date falls in the last seven days. Paginate until there are no more results. Also pull the prior seven-day window so the agent can compare week over week.

2. Synthesize across the open-text answers from all forms combined. The agent should produce: a one-paragraph TL;DR of the week, the top recurring themes with a response count for each, a sentiment summary that explicitly calls out any shift versus the prior week, three to five standout quotes worth sharing verbatim (with the form name they came from), and a list of individual responses that look like they need a human follow-up (urgent bugs, churn risk language, named complaints, anything time-sensitive).

3. Post the digest to the configured Slack channel using Slack Send a Message. Format it with Slack mrkdwn, broken into clear sections in this order: TL;DR, Top Themes (with counts), Sentiment vs Last Week, Notable Quotes, Needs Follow-Up. Keep it scannable, use bullets, and link back to Tally where useful.

4. Also create a new page in the configured Notion database using Notion Create a Page. Title the page with the date range (for example, "Weekly Feedback Digest, May 19 to May 25"). Put the full digest in the page body as headings and bullet lists so it is readable and searchable later. If the database has a Date property, set it to the Monday of the week being reported.

Edge cases to handle: if zero submissions arrived in the past seven days, still post a short Slack note and create a Notion page that says the week was quiet, so the team knows the workflow ran. If Tally pagination returns a large volume, summarize themes from the full set rather than truncating. Never include personal contact details in the public Slack post unless the submitter explicitly asked to be contacted.