Turn beehiiv poll answers into a weekly content brief
Every Friday at 3pm, read your beehiiv poll responses from the past week and drop a themed content brief in Slack and Notion for editorial planning.
beehiiv
Slack Bot
NotionMarketingProductAI ReportsContent GenerationFeedback TriageEvery Friday at 3pm (operator-local, adjustable), run an agent that turns my beehiiv audience's own words into a content brief for next week. This is an agent workflow, not code.
Trigger: cron, Fridays at 3pm.
Step 1. Call beehiiv List Polls on my publication and identify every poll that received at least one new response in the last 7 days. For each of those polls, call beehiiv Get Poll to fetch the question text and vote counts, and beehiiv List Poll Responses to pull the actual reader answers (both structured choices and free-text where present).
Step 2. If no polls received new responses in the last 7 days, stop the run silently. Do not post to Slack or Notion on empty weeks.
Step 3. Reason across all responses to synthesize what readers are actually asking for. I care about: recurring themes, contrarian takes, confusion or complaints, and specific story or topic requests. Group findings by theme, quote 2 to 4 representative reader responses verbatim per theme (keep quotes short), and finish with 3 to 5 concrete post ideas the content team could write next week.
Step 4. Post a short digest to Slack using Slack Bot Send a Message into a designated channel (make this a configurable input, default #content). The Slack version should be scannable: theme headers, a couple of quotes per theme, and the post ideas at the end.
Step 5. Append the same brief, dated with the week ending date, to a designated Notion content-ideas page using Append Block Children. Make the Notion parent page ID a configurable input. On the very first run, if the parent page ID input is blank, create the page with Notion Create a Page under a configurable parent page, name it "Reader Voice: Weekly Content Brief", and remember its ID for subsequent runs. Every following week appends a new dated section under the same page so the history stays in one place.
Configurable inputs to expose: the beehiiv publication ID, the Slack channel, the Notion parent page ID (nullable, auto-created on first run), and the lookback window in days (default 7).
Integrations to use: beehiiv (List Polls, Get Poll, List Poll Responses), Slack Bot (Send a Message), Notion (Create a Page on first run, Append Block Children on every run).
Additional information
What does this prompt do?
- Reads every beehiiv poll your audience answered in the last seven days.
- Groups reader replies into themes, contrarian takes, complaints, and specific topic requests.
- Posts a short digest to Slack with a few quoted reader responses so the team hears the audience in their own words.
- Appends the same brief to a Notion content-ideas page so every week is preserved for editorial planning.
- Ends each brief with three to five concrete post ideas the team can write next week.
What do I need to use this?
- A beehiiv account with a publication that runs polls.
- A Slack workspace and a channel where the content team lives.
- A Notion workspace with a parent page where the running content brief can live.
How can I customize it?
- Move the schedule if Friday afternoon does not fit your editorial rhythm.
- Point the digest at a different Slack channel or a DM to a specific editor.
- Choose which Notion page collects the running list of briefs, or let it create one on the first run.
- Change the lookback window if you want to synthesize a longer or shorter stretch of reader replies.
FAQs
What happens on weeks when no one answered a poll?
Where does the finished brief show up?
Does this work if we only run a poll every few weeks?
How does it pick which reader quotes to include?
Will old poll responses keep showing up week after week?
Related templates
Every weekday morning, check that every Stripe payout actually landed in your Mercury account, and hear about it only when one did not.
Every weekday morning, get a Slack digest of the social posts still waiting on sign-off, with the ones about to go live flagged first.
Every Monday morning, last week's support tickets become a themed Miro board, so your product team can see what customers actually complain about.
Every weekday we find the contracts still waiting on a signature, resend the ones going stale, and post a prioritized chase list to Slack.
Every weekday at 6pm, any board your team edited today becomes a readable Notion write up, so the people who missed the session can catch up.
When a contract is fully signed, we read the agreed terms, move the matching HubSpot deal to closed won, and post a deal desk summary to Slack.
Stop guessing what your readers want next.
Connect beehiiv, Slack, and Notion once, and every Friday your content team gets a brief written in your readers' own words.