Turn Form Responses Into a Weekly Digest With AI

Your form has been collecting answers for three weeks. You know this because your inbox told you, 47 separate times. You have actually read about four of them.

That is the real failure, and it has nothing to do with the form. The submissions arrived fine. The reading never happened, because nothing in the setup was designed to be read. What you want, once a week, is one short thing that tells you how many people wrote in, what they kept saying, and which three of them are still waiting on you.

One email per submission is not a system

The three defaults all fail in the same quiet way.

• The notification email turns every response into an interruption with no context. Fifteen of them in a week and you start archiving on sight, including the one from the person with a budget.
• The dashboard is a place you have to remember to visit. You visit it the day you launch the form and then roughly never.
• The CSV export is real data, correctly formatted, sitting in a Downloads folder. Nobody opens a CSV to find out how their week went.

A digest fixes this because it inverts the direction. Instead of the data waiting for you to come and interpret it, you ask one question on a Monday and get back something already interpreted.

Pull the week, not the whole form

Brieform's get_responses tool is what your AI client calls to fetch submissions. You do not call it yourself, you ask for the responses and the client handles it.

Two things worth knowing before you write the prompt.

• Under about 50 responses, the default JSON is fine. The whole week loads into the conversation and the model reads it directly.
• Past that, ask for the CSV URL format instead. You get a link to the export rather than several hundred rows dumped into the context window. The model fetches and reads the CSV, and your conversation stays fast. On the Free plan this rarely comes up (50 responses per month is the cap), but on Starter, with 2,000 responses a month available, a busy form crosses the line in days.

CSV export is on every plan, including Free, so the fallback path is never gated.

The Monday prompt

Save this once. Paste it every Monday. Change the form name and the qualifying rules to match your situation.

You are producing my weekly response digest for the form "Coaching intake" on Brieform. First, pull this week's responses with get_responses. If there are more than 50, request the csv_url format and read the CSV rather than loading every response into this conversation. Keep only submissions from the last 7 days. Then write the digest in exactly this order, and do not deviate. (1) Counts: total submissions this week, the change versus last week if you have it, and the per-step completion picture if the form is multi-step. (2) Themes: group the free-text answers into at most 6 themes. For each one give a short label, the number of responses that mention it, and one sentence explaining it. Sort by count, highest first. Any theme with fewer than 2 mentions goes under "Other". (3) Quotes: pick 3 to 5 verbatim quotes that carry the most information. Do not paraphrase, do not fix the grammar. Attribute each with a first name and the date. (4) Needs a reply: list every submission where the person asked a direct question, reported a problem, named a budget above 5k, or asked to be contacted. For each: name, email, one line on what they want, one suggested next action. If nobody qualifies, write "Nobody this week". (5) One thing I should change: a single sentence, based only on what is in the responses. Rules: do not summarise every response one by one. A response only appears if it changes a count, supports a theme, or lands in the needs-a-reply list. Never speculate about what someone meant. Keep everything except the needs-a-reply list under 400 words. Plain text, no preamble.

The length of that prompt is the point. A vague "summarise my form responses" gives you a wall of polite paraphrase. The constraints are what turn it into something you read in ninety seconds.

What makes a digest useful instead of decorative

Most AI summaries of form data fail for one reason: they restate every response in slightly shorter words. Twenty responses in, twenty bullets out. That is not a digest, that is the same reading job with extra steps.

The order in the prompt is deliberate.

• Counts first, because that is the only line you will read on a bad week. Twelve responses versus four last week is a decision. "Respondents expressed varied interest" is not.
• Themes with mention numbers, because "6 people asked about pricing" tells you what to fix and "several people mentioned pricing" tells you nothing. Force a number next to every theme.
• Verbatim quotes, unedited, because the model's paraphrase always sounds more reasonable and more articulate than the person did. The awkward original sentence is the useful one.
• An explicit needs-a-reply list with names and emails, because this is the part that actually costs you money when it goes missing. Everything above it is context. This is the to-do list.
• A hard word limit, because a digest that grows with your response volume defeats itself. 200 responses should produce the same length as 20, just with better numbers behind it.

Same prompt, but it writes itself into Notion

Brieform has no native Notion integration, no Slack app, no Zapier connector. That is on purpose. The AI client you are already talking to is the bridge, so you connect Brieform and Notion to the same client and ask for the handoff in the same breath.

Run my weekly digest for "Coaching intake" exactly as saved, then write it into Notion. Create a page in the "Weekly digests" database, titled "Coaching intake, week of [Monday's date]". Counts and themes as headings and bullets in the body, the quotes as a quote block, the needs-a-reply items as a to-do list so I can tick them off. Set the Status property to "To review". Then post just the counts line and the needs-a-reply names back to me here, so I know whether to open the page.

Swap Notion for Slack and the same shape works: post the digest into #inbound, tag yourself on the needs-a-reply names. No middleware, no per-task pricing, available on Free.

Where this pattern is the wrong one

This is a pull model. You ask, it answers. Nothing fires on its own unless your AI client has scheduled tasks, in which case you can point a recurring Monday task at the saved prompt and it will run without you. If your client does not support that, the digest happens when you remember to ask for it, which for most people is fine and for some people is exactly the problem.

Brieform also has no outbound webhooks. Nothing gets pushed anywhere the moment a form is submitted. So if you need an instant alert every time a lead worth five figures comes in, this pattern is the wrong one and you should not try to bend it into shape. Use a form builder with native webhooks or a Zapier trigger, and keep the weekly digest for the reflection layer, not the alerting layer. Those are two different jobs and one prompt cannot do both.

🚀 Try it now — Build a form and read it weekly with Brieform →

Free to start. No credit card required.

FAQ

How many responses can the AI summarise at once?

Under roughly 50, the responses load straight into the conversation. Past that, ask for the CSV URL format so the model reads the export instead of filling the context window with rows.

Does the digest run automatically every Monday?

Only if your AI client supports scheduled tasks. Brieform itself has no scheduler and no outbound webhooks, so on its own this is a pull model: it runs when you paste the prompt.

Can I send the digest to Slack instead of Notion?

Yes, and the mechanism is identical. Connect Slack to the same AI client, then tell it where to post. There is no native Brieform Slack app, the client does the handoff.

What does this cost?

Free is $0 with 1 published form and 50 responses per month, which is enough to test the pattern. Starter is $29/mo ($23/mo annual) for 20 published forms, 2,000 responses per month and analytics. Pro is $69/mo ($55/mo annual) for unlimited. CSV export is on every plan.

What data ends up in the digest?

Whatever your form collects, plus country, city and a browser summary. Brieform stores no raw IP addresses on responses, and everything is hosted in the EU (Frankfurt).