Weekly Manychat feedback digest to Notion and Slack

Every Friday at 4pm in my local timezone, build a weekly product feedback digest from Manychat, write it to Notion, and ping our product team in Slack.

Set up: at the start of the run, call Manychat's Get Custom Fields once to resolve which custom-field IDs hold feedback text. The likely names are feedback_text, review_text, and nps_comment, but read the page's real custom fields and match by name. Also call Manychat's Get Tags so the agent can recognize feedback-signal tags such as feedback, nps, review, or bug_report.

Collect feedback for the last 7 days. For each feedback custom field, use Manychat's Find Subscriber by Custom Field to pull every subscriber whose value is non-empty. Also include any subscribers carrying the feedback-signal tags identified above. De-duplicate by subscriber ID. For every subscriber in the combined set, call Manychat's Get Subscriber Info to fetch the full profile, custom field values, and tags.

Filter to feedback created or updated in the last 7 days based on the subscriber's last_interaction or last_growth_tool timestamps and the custom-field last-updated time when available. If a subscriber's feedback predates this window, drop them.

If the resulting set is empty, exit cleanly without writing to Notion or posting to Slack. Skipping quiet weeks is correct behavior.

Otherwise, analyze the feedback. Categorize every piece into one of: bug, feature request, pricing, onboarding friction, praise, or other. Then cluster recurring themes (e.g. 'onboarding video too long', 'wants Stripe integration', 'pricing confusion on the team plan'). Pick the top 3 themes by how many subscribers mentioned them. For each theme, choose 1-2 representative direct quotes with the subscriber's first name and Manychat handle.

Write the digest using Notion's Create a Page into our product feedback database (ask me for the database ID on first run, then remember it). Use a consistent page format so the database reads like a running log:

- Title: 'Manychat feedback digest, week of <Mon DD>' - Top of page: a 2-3 sentence summary of the week (volume, dominant categories, mood). - Section 'Top 3 themes': for each theme, a heading with the theme name, 1-2 quotes (italicized), the subscriber handles, and a one-line recommended follow-up. - Section 'Category breakdown': counts for bug, feature request, pricing, onboarding friction, praise, other. - Section 'All feedback': a bullet list of every quote with category tag and subscriber handle. - Section 'Recommended follow-ups': 3-5 concrete next steps for the product team.

After the Notion page is created, post to our product Slack channel using Slack Bot's Send a Message. Default channel is #product-feedback (ask me on first run, then remember). The Slack message should be short: one line of context, the top 3 themes as bullets with the subscriber counts, and a link to the Notion page. Keep the message under ~6 lines.

Important constraints: keep the Notion page format identical week over week, do not invent feedback or paraphrase quotes (use direct text from the custom field), and skip the run cleanly with no Notion or Slack output if there is no new feedback. Always include the subscriber handle next to every quote so the team can follow up directly.

Additional information

What does this prompt do?

Pulls every Manychat subscriber who left feedback in the last 7 days, including their profile, tags, and the full text of their comment.
Groups the week's feedback into clear buckets like bugs, feature requests, pricing pushback, onboarding friction, and praise, then surfaces the top three themes with real quotes.
Writes a tidy weekly entry into your product feedback database in Notion with sections for themes, top quotes, and recommended follow-ups.
Posts a short summary plus the Notion page link to your product Slack channel so the whole team sees it before the weekend.
Skips quiet weeks instead of posting an empty page, so the channel never gets noise when there's nothing new.

What do I need to use this?

A Manychat account where customers leave feedback in a custom field (for example feedback_text, review_text, or nps_comment).
A Notion workspace with a product feedback database, shared with your General Input connection.
A Slack workspace and a channel where the digest should post, like #product-feedback.
Optional: a tag or two in Manychat that marks feedback subscribers, so nothing slips through if the custom field is blank.

How can I customize it?

Change when it runs. Friday at 4pm is the default, but you can move it to Monday morning, swap to a two-week cadence, or tie it to your sprint review.
Tune the categories. Add a 'mobile app' bucket, split 'pricing' from 'plan limits', or merge 'praise' into a single highlight section.
Pick where it posts. Swap the Slack channel, DM a specific PM, or skip Slack entirely and only update Notion.
Adjust what counts as feedback. Point it at different custom fields, add Manychat tags like vip or beta, or filter by language or channel.

Frequently asked questions

What if no one left feedback this week?

The workflow skips posting entirely. No empty Notion page, no Slack noise. You only hear from it when there's something real to read.

Do I need a special Notion template?

No. Point it at any Notion database you use for product feedback and the agent will write a consistent weekly page with themes, top quotes, and follow-up ideas. The format stays the same week over week so it reads like a running log.

Which Manychat fields does it read?

Any custom field that holds feedback text, such as feedback_text, review_text, or nps_comment. You can also include subscribers tagged with things like feedback or nps so nothing gets missed.

Can I change the Slack channel or skip Slack entirely?

Yes. The Slack ping is optional. You can change the channel, DM a specific person, or remove the Slack step if Notion alone is enough.

How are the top three themes chosen?

The agent clusters the week's feedback by topic and ranks themes by how many subscribers mentioned them, then picks one or two representative quotes per theme along with the subscriber's handle.