Describe the survey. Get a real one.
Not a list of text boxes. Branching logic, limited places, scored answers, calculated fields and routed outcomes — the parts that make a form actually work, built for you.
Free, no card. Every editor is free, with no trial timer — and a free account gets Lumen Core plus a monthly AI allowance.
- Price
- Free to buildPublishing needs Plus and above
- Logic
- Real branchingSkip, route and score
- Quotas
- Limited placesEnforced server-side
- Outcomes
- Routed endingsDifferent result per path
The parts of a form that are actually hard.
Anyone can put four text boxes on a page. Quotas, scoring, calculated fields and routed outcomes are where a survey stops being a questionnaire and starts being a system.
Every field type, properly configured
Choice, matrix, ranking, scale, slider, file upload and statement blocks — each with the options that make it useful rather than a generic input.
- Picture choices with emoji or image cards
- Matrix questions with multi-select rows
- File uploads with type, count and size limits
Questions that depend on answers
add_logic builds real branching — skip ahead, jump to a section, or end the form early — so nobody is asked a question that does not apply to them.
- Skip and jump based on any earlier answer
- Early endings for respondents who do not qualify
- Calculated fields from stable keys you can reference
It remembers what they already said
Recall an earlier answer inside any later label, description or confirmation with a {{key}} token — with a fallback for while it is still unanswered.
{{name|there}}— the fallback shows until they answer- Calculated fields compute over the same keys —
{{price}} * {{qty}} - Works in the confirmation, so the ending is personal too
Limited places, enforced properly
Option quotas turn choices into real capacity — session sign-ups, interview slots, first fifty only — and they are enforced server-side, not hidden in the browser.
- Per-option limits that close when full
- Enforced server-side, so it cannot be bypassed
- Lead scoring points per choice for qualification
It looks like yours
design_theme builds a coherent theme rather than swapping an accent colour, and generate_cover gives the form a real opening rather than a bare first question.
set_theme·design_theme·generate_coverset_welcomefor a proper opening screen- Statement blocks with images or embedded video
Answers you can act on
Outcomes route respondents to different endings based on what they said, and read_responses lets the agent analyse what came back.
set_outcomes— a different ending per pathread_responsesto summarise or chart the results- Push results into a sheet via the library bridge
A research survey, built and gated before it goes out.
LumenForms has no planner, so there is no phase card here — just the tools, in order. The stop comes at the end, where it always should: before a form is published and emailed to real people.
The list is in a sheet. The brief is in a doc.
Building a form means reading things that already exist somewhere else, and putting the answers somewhere useful afterwards. Both directions run through the same bridge.
search_library searches every saved document — PDFs, sheets, decks, boards, forms and notebooks — not just the one that is open.
work_on_document passes the job to that document’s own AI, so a spreadsheet is built by the spreadsheet engine rather than guessed at from outside.
create_document spins up a new doc, sheet, PDF, deck or note from what it just made, and opens it in the right editor.
What LumenForms actually does.
Question types
The full set, not the easy four.
- Choice, checkbox, dropdown, ranking
- Matrix with single or multi-select rows
- Scale and slider with end-cap labels
- File upload with type, count and size limits
Behaviour
What separates a form from a questionnaire.
- Branching logic — skip, jump or end early
- Option quotas enforced server-side
- Lead scoring points per choice
- Calculated fields from stable field keys
Publishing
Deliberately the gated part.
- Free to build and preview end to end
- Publishing and sending need Plus and above
- Both ask first, as a capability of their own
- Responses readable by the agent once they arrive
LumenForms questions.
Is LumenForms free?
Building, designing and previewing a form is free with no trial timer — you can walk the whole thing end to end including branches and outcomes. Publishing it to the web and emailing it to a list need a plan that includes Forms (Plus and above), which is why the demo above stops at exactly that point.
Are quotas actually enforced?
Yes, server-side. An option with a quota closes when it fills, so "first fifty only" or a limited interview slot genuinely limits — it is not a count kept in the respondent’s browser.
Can it build the form from something I already have?
That is the normal case. search_library finds the brief, the recipient list or last quarter’s version among your saved documents, and read_library_document reads it back in full before any question is written.
What happens to the responses?
read_responses lets the agent read what came back so it can summarise or chart it, and the library bridge can push the results into a real LumenSheets workbook — with formulas, not a static table — for whatever analysis comes next.
Build the whole thing free.
Logic, quotas, scoring and outcomes. Publish it only when you are ready.
Free, no card. Every editor is free, with no trial timer — and a free account gets Lumen Core plus a monthly AI allowance.