Inputs
Questions, answer types, conditional rules, validation, visual settings, access requirements and publication dates.
Build structured questionnaires and data-capture forms with validation, access controls and exportable responses.
A survey is stored as an editable Cloud service, while each submission becomes structured response data connected to that definition.
Questions, answer types, conditional rules, validation, visual settings, access requirements and publication dates.
Individual submissions, aggregate response data, completion status, exports and supported webhook events.
The questionnaire remains editable and reusable; new versions preserve the service while collected responses stay available for review.
The service separates form design, publication and analysis so that changing a question does not become a manual data-processing task.
Translate the objective into questions, answer formats, required fields and validation rules.
Add conditional branches, access controls, visual identity and completion messages for the intended audience.
Open the service during the required period and receive validated responses through its public URL.
Filter submissions, export structured data and trigger supported integrations for downstream work.
Combine text, choice, rating, date, file and structured fields in the order required by the process.
Show relevant questions according to previous answers and keep shorter paths for each participant.
Control mandatory fields, accepted formats, ranges and response rules before a submission is accepted.
Configure visual styles, introduction and completion messages, public dates and the final shareable URL.
Use public access, OTP or external authentication and apply response or participant restrictions.
Review submissions, export structured data and send supported events to external systems through webhooks.
Useful forms need reliable participation rules, data ownership and a clear path from each response to the systems that use it.
Control field types, mandatory answers, branching, ordering and validation without asking participants for irrelevant data.
Choose open participation, OTP or external authentication and combine it with publication windows and response limits.
Keep submissions associated with the owning account, review them centrally and export only the data required for the next process.
Use exports and supported webhooks to move validated responses into CRM, support, analytics or internal workflows.
The same builder supports different objectives because the questions, identity rules and output handling remain configurable.