Weekly Gravity Forms feedback digest to Slack and Linear

Every Monday at 9am, roll up last week's responses from my Gravity Forms customer feedback survey into a written digest for the product team and file follow-up work in Linear for the items worth acting on.

Trigger: cron, weekly at Monday 9am in my local timezone.

Step 1. Use Gravity Forms List Entries by Form to pull every entry created in the last seven days from my survey form. Make the form ID configurable so I can point it at our NPS form, CSAT form, or general feedback form. Read the relevant text fields (open-text comments, the score, and any tag or category fields).

Step 2. Cluster the responses into recurring themes, summarize overall sentiment (and the score distribution if it is an NPS or CSAT form), and pull out two or three standout quotes that capture how customers are feeling this week.

Step 3. Use Slack Bot Send a Message to post the digest in a configurable channel for the product team. Format it so it reads well in Slack: a one-line headline, the sentiment summary, the recurring themes, two or three standout quotes, and a short list of the Linear issues that were just filed with links.

Step 4. For every individual response that contains a concrete bug report, churn risk, or specific feature ask, use Linear Create Issue to open a ticket in a configurable team. Use a one-sentence summary as the title, include the verbatim quote in the description, suggest a team or label, and note the original Gravity Forms entry ID so I can trace it back to the source response.

Judgement calls the agent should make:

- Skip Linear issues for vague praise, generic complaints, or low-signal noise. Bias toward fewer, better-scoped issues that someone on the team can actually pick up.

- Do not file duplicate issues when the same theme shows up across multiple responses. Group them into a single issue with a representative quote and a note about how many people raised it.

- If the week was quiet and nothing met the bar for a Linear issue, still post the digest in Slack so the team knows the survey was checked.