Survey

Description

Service for designing a public form with configurable questions, collecting responses, and analyzing results from Cloud.

Use cases

• Conduct opinion, satisfaction, or research studies.
• Collect requests, assessments, or structured data.
• Publish forms with a custom visual identity.
• Review statistics and export responses.

How to create the service

Open Cloud > New item, select Survey, enter its name and location, and complete the initial settings. Then use the editor to define questions, design, access, and publication.

Interface and controls

Editor tabs separate content, questions, styles, access, preview, and results. The builder adds, orders, duplicates, and removes questions and choices. The shared Cloud selector inserts images. Header actions provide save, preview, publication, and other available commands; the responses page includes filters, details, statistics, and export.

Full workflow

1. Define the form's purpose, title, description, and language.
2. Add questions, choices, required states, and validations.
3. Configure design, header, and images.
4. Set status, dates, limits, and available access methods.
5. Submit a preview response and correct the flow.
6. Publish and share the URL or embed code.
7. Review responses, statistics, and exports.

Supported files or data

The service stores questions, choices, rules, and submitted answers. It supports the question types enabled in the builder, including text and selection fields. Images come from compatible Cloud files. Tabular export formats depend on the results page catalog.

Configuration options

Options include title, description, questions, choices, required fields, validation, order, text, colors, typography, spacing, images, publication status and period, response limits, authentication, OTP or identity providers when enabled, messages, and post-submit behavior.

Output and export formats

The result is a public page and a structured response set with aggregate statistics. Responses can be exported in available tabular formats, normally CSV, XLSX, ODS, JSON, XML, HTML, or PDF, depending on system configuration.

Saving, downloading and sharing

Saving updates the service and may create a previous version. Share the survey through its public link or embed after publication. Users grants access inside Apification. Responses are downloaded from the results page, not from preview.

Limits and technical requirements

Configured plan, credit, response, date, and storage limits apply. Public submissions require a published service within its active period. OTP and external providers require credentials and connectivity. Changing questions after collecting responses can break historical comparisons.

Common errors

• The survey rejects responses: check status, dates, limits, and access requirements.
• An image is missing: confirm that the Cloud file still exists and is selectable.
• A question does not validate: review required status, choices, and field format.
• Export data is missing: check filters and whether responses use an older question version.

Privacy and data processing

Explain purpose, legal basis, retention, and recipients before collecting personal data. Request only necessary information and restrict response access. Configure authentication for non-public forms and do not place sensitive data in URLs.

Frequently asked questions

• Can I test without publishing? Yes, use Preview and keep tests separate from real responses.
• Can a published question be edited? Yes, but its meaning should not change after responses exist.
• How can repeated participation be reduced? Use available access restrictions; an open mechanism cannot guarantee identity on its own.

Related services

Poll for a closed decision, Event for registrations, Landing for lead capture, Coupons for code assignment, and Spreadsheet for further analysis.