Weekly Gravity Forms NPS Digest with Linear Follow-ups

PromptCreate

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.

What does this prompt do?

Pulls last week's responses from your Gravity Forms NPS or customer feedback survey.
Posts a written digest in Slack with recurring themes, overall sentiment, and the quotes that matter.
Files a Linear issue for every concrete bug report, churn risk, or feature ask, with the verbatim quote attached.
Stays quiet on vague praise and noise so the backlog only fills up with work that is worth doing.

What do I need to use this?

A WordPress site running Gravity Forms with an active NPS, CSAT, or general customer feedback form.
A Slack workspace and a channel where the product team wants the Monday digest to land.
A Linear workspace and the team you want bug reports, churn risks, and feature asks filed into.

How can I customize it?

Change when it runs. Default is Monday at 9am, but you can shift the day, time, or run it biweekly.
Swap which Slack channel gets the digest, or fan it out to more than one channel for different stakeholders.
Tune how strict the agent is about what becomes a Linear issue versus what stays in the Slack digest.

FAQs

Does this work with any Gravity Forms survey?

Yes. Point it at your NPS form, CSAT form, or a free-form feedback form and the agent reads whichever fields you have, including the score and the open-text comments.

What stops the agent from spamming Linear with junk issues?

The instructions tell it to skip vague praise and low-signal complaints, and to only file issues for concrete bugs, churn risks, or specific feature asks. If a theme shows up across multiple responses, it groups them into one issue instead of many.

Can it run more often than weekly?

Yes. You can ask for daily or biweekly instead, and the time window the agent looks back over changes to match so nothing gets double-counted.

Will old responses get filed as Linear issues every week?

No. The agent only looks at responses created in the last seven days, so each piece of feedback is reviewed once when it first comes in.

What happens on a quiet week with no concrete asks?

It still posts a short digest to Slack so the team knows the survey was checked, even if no Linear issues were filed that week.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

+1

Agentic Task

Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Agentic Task

Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agentic Task

Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Agentic Task

Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Agentic Task

Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.