Typeform StrawberryRead all 1,900 free-text survey answers this afternoon
A companion clusters the column nobody opened into themes, keeps a real quote and the response id under each, and writes the summary into the sheet you already use.
The churn survey worked. Nineteen hundred people answered, the multiple-choice results were in a dashboard by Friday, and the last question, “anything else you want to tell us?”, has been open in a tab ever since. That column holds the actual reasons.
A companion reads all nineteen hundred this afternoon. It pulls the responses for the period you name, groups the free text into themes it can defend, keeps real quotes attached to each, and writes the summary into the Google Sheet that already holds your cohort formulas.
1,900 answers, clustered, quotes attached
The companion groups the free text into themes it can defend, including the awkward one that is 4% of replies and entirely enterprise accounts. Each theme carries real quotes and the response behind them, so you can push back on the grouping.
Then it writes into Google Sheets natively, so the summary lands in the workbook with your cohort formulas. The response payload carries every field, so a theme can be cross-cut by the multiple-choice question before it. The wider mechanics are in data extraction.
Can a companion build the form as well as read it?
It creates a form from a title and fields and updates an existing one, so the drafting loop is fast: describe the study, get a form back, argue with the wording, iterate. It reads the full definition first, so an update changes only what you meant to change.
Question wording is where you stay involved. Leading phrasing, a missing option, a scale with no neutral point: that is how a survey hands back the answer you were hoping for. A companion drafts and you edit, the same split that works for marketing research.
Webhooks: where the loop closes
New responses reach whatever you have listening the moment they land.
The integration lists the webhooks on a form and creates or replaces one by tag, so the destination is your own endpoint, an automation, or a queue.
The companion half is the interesting one. Responses arrive continuously, a routine reads them, and the ones that need a person, an angry answer, a named account, a request that is really a support ticket, get surfaced the same day.
Which actions should stay off a routine?
Deleting a form.
It is permanent and it takes every response with it, so it waits for your explicit approval and belongs nowhere near a scheduled run.
Publishing changes to a live form is the second. Changing fields mid-collection splits your dataset into before and after, so a companion makes that edit only when you ask for it. A new form is often the cleaner move.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents