Reusable forms
Build a form once and embed it across websites.
Build once and collect responses together
Build branded website forms and collect every response in one inbox.
A builder with 25 question types (choices, rating, NPS scale, slider, matrix, ranking, file upload, signature, consent, calculation, hidden values, page breaks), rules on earlier answers matched all or any, steps that are skipped unless their rules pass so one form branches into paths, answer piping, a one-question-at-a-time layout, saved progress, and drafts that reach websites only when published. 195 templates fill in the brand, and Claude builds, tailors or changes a form from a sentence in the brand's voice. Each domain's forms follow its brand DNA from Brand Kits (colours by role, fonts, logo, corner radius, shadow, voice) with the shape language tuned per domain. embed.js puts a form inline (sizing itself), behind a popup button or in a floating side panel on any site, framework or builder; a plain iframe, a plain HTML form and a JSON API need no script. Responses land in an inbox with search, spam, files in R2 and CSV export, in analytics with per-question breakdowns and NPS, in team emails, in copies to respondents, in signed webhooks and, when asked, in Enquiries; Claude can add a summary, category and priority to each response and summarise them all. Honeypot, timing, known-spam rules, rate limits, optional Turnstile and per-form allowed websites guard every form.
What Forms does for you.
Build a form once and embed it across websites.
Present forms in the website’s brand.
Keep every response in one inbox.
A suggested path for Forms. What you can do depends on your access in the app.
Choose the information the form needs to collect.
Check the brand styling and website placement.
Open the inbox to inspect submitted responses.
Live host, inventory, governance, health checks, verification, dependencies and history.
A builder with 25 question types (choices, rating, NPS scale, slider, matrix, ranking, file upload, signature, consent, calculation, hidden values, page breaks), rules on earlier answers matched all or any, steps that are skipped unless their rules pass so one form branches into paths, answer piping, a one-question-at-a-time layout, saved progress, and drafts that reach websites only when published. 195 templates fill in the brand, and Claude builds, tailors or changes a form from a sentence in the brand's voice. Each domain's forms follow its brand DNA from Brand Kits (colours by role, fonts, logo, corner radius, shadow, voice) with the shape language tuned per domain. embed.js puts a form inline (sizing itself), behind a popup button or in a floating side panel on any site, framework or builder; a plain iframe, a plain HTML form and a JSON API need no script. Responses land in an inbox with search, spam, files in R2 and CSV export, in analytics with per-question breakdowns and NPS, in team emails, in copies to respondents, in signed webhooks and, when asked, in Enquiries; Claude can add a summary, category and priority to each response and summarise them all. Honeypot, timing, known-spam rules, rate limits, optional Turnstile and per-form allowed websites guard every form.
Free-text enquiries belong to Enquiry.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
forms.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.