turn typeform answers into a useful intake brief
find the intake forms that need a follow-up before you promise anyone a call. a typeform bot in dusk can read responses alongside the questions and branching rules.
ask it to pull out the requested service, timing and missing details. keep each response id beside its summary so you can open the original.

what a bot can do in Typeform
read the question the respondent saw. the word “other” means little without its field and choices. use the form definition to match each answer to its prompt. use the response type to decide which submissions belong in the brief.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| Get Workspace | read | confirm which workspace owns the client intake forms |
| List Forms | read | find the active intake form among similarly titled copies |
| Get Form | read | read field definitions and follow the branches between questions |
| Get Form Responses | read | select completed responses in a date window and page through the results |
| Get Form Messages | read | inspect custom button labels and error messages during a wording review |
| Patch Form | change | apply a chosen change to a form setting without replacing the whole form |
composio, the connection service behind dusk bot's apps, lists 35 Typeform actions (version 20261101_00, read 20 november 20263). dusk bot treats 16 as reads, 0 as sends and 19 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, and waits for your Allow unless you set a daily amount.
connect Typeform
- open Connected apps in the sidebar.
- pick Typeform and sign in on Typeform's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Typeform.
- ask in plain words. reading and drafting happen freely; sending asks you first.
use the form id from the live intake form. connect typeform to your bot and choose read only. give it your reporting time zone and the questions that matter to the handoff. try an answer from a short branch before scheduling the summary.
routines to copy
choose the cutoff before you count responses. the retrieval action can take up to 30 minutes to show recent submissions. a morning review of yesterday gives late-arriving responses time to appear.
yesterday’s intake requests
every morning at 9, read all completed responses to my intake form submitted yesterday in my time zone. group them by requested service. include the response id, requested timing and one detail i need before a call. keep contact details out of the summary here.daily at 9 am · a service-by-service intake brief
why the budget field is empty
every monday at noon, review last week’s completed intake responses with no budget answer. read the form logic. separate responses whose answers skip the budget question from cases that need a follow-up. if the form changed since submission, mark any uncertain paths as unclear. give me response ids here.mondays at noon · a list of budget gaps worth asking about
form wording before the next cohort
on fridays at 10, read our intake form’s questions, choices and custom messages. look for error messages that ask for a different format from the question. quote both lines and propose a correction here. leave the live form alone.fridays at 10 am · pairs of conflicting instructions with suggested copy
what it asks you first
draft the wording in chat first. a suggestion can stay entirely in dusk. editing form settings, changing messages and deleting responses are writes without a send prompt. keep the bot read only or give an editing routine the instruction “ask me before you change anything”.
what it cannot do
- guarantee the last few minutes are complete. recent responses may take up to 30 minutes to appear in a response lookup.
- recover an unspoken reason for a blank field. form logic can explain a skipped question. an unexplained blank stays an open question.
- use the all-files download for just one respondent. that action retrieves an archive of uploads for the entire form. these reviews need no file download.
when to ask the respondent
let the person supply the missing fact. if the client chose a service but left the deadline open, carry that question into the call. if you just need to read one submission, open it in typeform. the bot earns its place when you need to compare submissions and branches.
what it looks like
a fictional example.
before
ruth nolan chooses the consultation option. the intake form only asks for a delivery address on the installation branch.after the bot
consultation request: no address follow-up. ruth’s answer skips installation. ask about the preferred call date instead.an illustration with made-up names and numbers.
questions
can i count just the people who finished the form?
choose completed responses and a submission window. ask for all result pages and the total used in the brief. keep partial responses out of that count.
can this tell me which question people found confusing?
it can identify wording worth reviewing. a confusing instruction and an empty answer are clues. ask respondents before concluding why they stopped.
sources
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].
prepare a client onboarding brief before kickoff
read yesterday’s typeform answers in one short summary
a google sheets bot that flags low stock by row
turn a calendly booking into an opening question
an airtable assistant that learns the table before writing
a calendly bot that brings the booking details to the call