Weekly Fillout feedback digest with Linear issues and a Slack summary

Every Monday, cluster last week's Fillout form responses into themes, file the important bugs and feature requests in Linear, and drop a clear summary in Slack.

Agentic Task
FilloutLinearSlackProductCustomer SupportFeedback TriageDaily DigestsAI Reports
PromptCreate

Build an agent workflow that triages our Fillout feedback form on a weekly schedule and turns it into a Slack digest plus Linear issues for the things worth acting on.

Trigger: cron, every Monday at 9am in the org's timezone.

Inputs the user should configure when launching the workflow:

- Fillout form ID (the feedback form to read from).

- Linear team ID where new issues should land, plus optional default labels and priority.

- Slack channel ID where the digest should be posted.

- Threshold for filing a Linear issue. Default: 'mentioned by more than one respondent, or explicitly flagged as blocking.'

Steps the agent should follow each run:

1. Call Fillout List Form Submissions on the configured form, filtered to the last 7 days using the afterDate and beforeDate query params. Paginate until all submissions in the window have been fetched.

2. If there are zero submissions, skip step 3 and 4 and just post a short Slack note like 'No new feedback submitted this week.' Then stop.

3. Read through every response and cluster them into themes: bugs, feature requests, praise, and confusion. For each cluster capture (a) a count, (b) two or three representative verbatim quotes with the submitter's email, and (c) a one-line summary of the theme.

4. For any bug or feature request that meets the configured threshold, call Linear Create Issue in the configured team. Title should be a short, action-oriented summary of the theme. Description should include the theme summary, the submitter emails, and the quoted feedback so engineering can follow up. Apply the configured labels and priority if provided. Collect the issue URLs to include in the digest.

5. Also compare this week's counts per theme against last week's counts so the digest can call out sentiment trend (up, down, flat). If there is no prior-week baseline yet, say so instead of guessing.

6. Call Slack Send a Message to post the digest to the configured channel. The message should include: total submissions this week, counts per theme, the top three quotes across the whole week, the sentiment trend versus last week, and a bulleted list of any Linear issues opened with their URLs.

Keep quotes short and unedited. Do not paraphrase what the customer said. If a response is off-topic or empty, drop it from the analysis instead of stuffing it into a theme.

This is agent work because the clustering, threshold judgement, and quote selection are open-ended.

Additional information

What does this prompt do?
  • Pulls every submission from a designated Fillout feedback form for the past 7 days.
  • Reads through the responses and groups them into themes like bugs, feature requests, praise, and confusion, with representative quotes for each.
  • Files a Linear issue in your chosen team for any bug or feature request that shows up more than once or is flagged as blocking, including the submitter emails and their exact words.
  • Posts a Slack digest with counts per theme, the top three quotes, a sentiment trend versus last week, and links to any issues that were opened.
What do I need to use this?
  • A Fillout account with access to the feedback form you want summarized.
  • A Linear workspace and the team where new issues should land.
  • A Slack workspace and the channel where the Monday digest should be posted.
How can I customize it?
  • Change the schedule. Monday at 9am in your org's timezone is the default, but any weekly or biweekly cadence works.
  • Adjust the threshold for filing Linear issues. The default is 'mentioned by more than one respondent, or flagged as blocking', but you can loosen or tighten it.
  • Pick a different Slack channel, tag a specific team lead, or add labels and a priority to the Linear issues it creates.

Frequently asked questions

What happens if no one submitted feedback last week?
The workflow skips Linear entirely and posts a short 'no new feedback this week' note in Slack so the Monday digest is still predictable.
Will it create duplicate Linear issues if the same bug keeps coming up?
You can tell it to check for a matching open issue before filing a new one, or to add the new quotes as a comment on the existing issue instead.
Can I use this for an NPS survey or a customer satisfaction form?
Yes. Any Fillout form works. The agent reads whichever questions you point it at and clusters the free-text answers into themes.
How does it decide what counts as a bug versus a feature request?
It reads each response in context and labels it based on the language people use. You can spell out your own definitions in the prompt to steer it.
Can the digest go to a private channel or a DM instead of a public channel?
Yes. Point it at whichever Slack channel, private channel, or direct message you want the Monday summary to land in.

Turn last week's feedback into next week's roadmap.

Connect Fillout, Linear, and Slack once, and every Monday you get a clean digest plus real issues filed for the things worth fixing.