Skip to app details
Back to app library
APPNEURAL APP FAMILYContent & Files

Forms

Build once and collect responses together

Build branded website forms and collect every response in one inbox.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
A branded form with clear fields
T
FormProject enquiry form
Workshop registration
Contact form
02 / CAPABILITIES

Built around the work you do.

What Forms does for you.

01

Reusable forms

Build a form once and embed it across websites.

02

Brand styling

Present forms in the website’s brand.

03

Shared responses

Keep every response in one inbox.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Forms. What you can do depends on your access in the app.

01

Build the form

Choose the information the form needs to collect.

02

Review the embed

Check the brand styling and website placement.

03

Review responses

Open the inbox to inspect submitted responses.

YOUR NEXT MOVE

Make Forms part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE2 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Branded forms for a connected domain, built from templates, embedded on the website, with responses and AI tailoring.

Free-text enquiries belong to Enquiry.

Priority
P2
Portfolio
Content & Files
Capability
Content & Files
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:04
Semantic inventory

Every number says what it counts

2Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

form schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

forms.appneurox.com DEPLOYED

forms.appneurox.com

Worker
forms-catalog
Health
HEALTHY
Last deployment
2026-11-03T12:41:02.000Z
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/forms-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app