read yesterday’s typeform answers in one short summary
“nobody asked for it” and “nobody answered the question” are different findings. this daily routine reads yesterday’s completed typeform submissions.
it counts choices on one question and groups the reasons people gave on another. the summary in chat shows how many people answered each question, so a blank field stays visible.

the message
paste this into a chat with your bot
every morning at 8, read yesterday’s completed responses for the typeform "alba street workshop survey" using submission time in my time zone. count choices for "preferred session" and summarize optional text for "reason for choosing". read the form to match the question fields. fetch every page of responses in that window.
in this chat, give the total submissions, the count for each selected choice and the blanks for each field. if branching can hide the question, label missing answers “no answer recorded”. group the text answers by reason. paraphrase one concrete example. leave names and contact details out. never edit the form or act on a response.
stay quiet for a complete day with zero submissions. if a page is missing or a field no longer matches, say what you could read and leave affected totals open.- when
- 8 am daily for the previous local calendar day, midnight to midnight
- needs
- typeform read only for the chosen form and its paginated responses3. replace the survey title and both question labels with yours.
what comes back
an example, not a real run
alba street workshop survey · yesterday · 8 completed
preferred session: saturday 4, sunday 3, blank 1.
reason for choosing: 4 answered, 4 blank. two mentioned shift times. one needs a late bus and one shares childcare.
example: a later start would leave time to get home after a night shift.make it yours
- keep the question wording beside the count. “which day can you attend?” and “which day do you prefer?” ask different things.
- allow multiple choices. for a pick-many question, count each option once per submission. label the totals as selections.
- drop the example for a tiny group. a rare detail can identify someone even after you remove their name.
when it goes wrong
- the newest responses appear late. typeform reads can lag by up to 30 minutes. give the last submission time to appear before running the summary.3
- a renamed question changes the meaning. inspect the current form field and reset the question you want before comparing days.
- a blank looks like a refusal. if only weekend visitors saw the question, weekday visitors had no chance to answer it. read the form logic before interpreting blanks.
use a count you can explain
put an answer beside the number of people who could have given it. four requests for a late start mean something different among five answers than among fifty. ask for the missing-answer count even when the total looks tidy.
if you need the exact wording of a complaint, read that submission in typeform. a paraphrase can lose the distinction that matters.
questions
does starting a form count as a response here?
count completed submissions only. someone who leaves halfway through stays outside this report. a completed submission can still contain blank optional fields.
can i use the summary for follow-up calls?
use the original response for individual follow-up. the daily note groups reasons and deliberately leaves identifying details out.
sources
- dusk bot docs: routines
- dusk bot docs: files and apps
- composio: typeform actions, checked 20 november 2026
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
turn typeform answers into a useful intake brief
prepare a client onboarding brief before kickoff
an ai market research bot that shows its sources