Changelog

All notable changes to the NueForm platform are documented here. This page covers API releases, new features, and important updates.

September 2026

Forms take responses only while they're published, on every channel

Released: September 28, 2026

An unpublished or never-published form now takes no submissions at all (on its page, in embeds or by phone), including responses someone had already started: only a phone call already in progress can still finish, and its response is delivered to you as usual unless the form is held for review or is rejected in review during the call, in which case it's held. A closed form refuses new responses, and respondents already filling it in can finish. When a form stops accepting someone's answers part-way through, they see the Form Closed screen instead of a thank-you screen, and a submission that fails for any other reason shows an error and a Try again button, never a thank-you screen. Web submissions are checked against the published version, so an answer to a published question is kept even if you've changed your draft since, and submissions no longer fail after you revert to an earlier version. ?preview=1 now shows the draft only to people who can edit the form, and records nothing. The Live / Closed button only opens or closes the live form: it no longer publishes pending edits. See Accepting Responses.

Phone calls now run on the form's published version, kept for the whole call. A number whose form is unpublished, closed or over the monthly response limit tells callers so and hangs up, and outbound calls and campaigns don't start on such a form. A campaign paused because its form stopped accepting responses stays paused until you resume it. When a Transfer sends a call on to a form that isn't accepting responses, the response to the first form is still completed. See Telephony.

All signers of a contract are shown the version that was published when the signing session was created, the same one the signed PDF prints: see Which Version Signers See. Sessions of an unpublished Fuse form can't be joined. A form held for content review sends no email steps, and its data nodes and payments are refused, until the review is done: see Forms Held for Review.

Account and sign-in protections

Released: September 28, 2026

A new sign-in method is connected to an existing account with the same email only when the account's address is confirmed and the new sign-in vouches for it; otherwise the person confirms by email. This replaces the We can't finish signing you in page for SSO sign-ins. Email changes now take effect only after the new address is confirmed, and sign-up refuses an address that already has an account or belongs to an SSO organization. An address that belongs to an SSO organization can't get an account through Google, Microsoft, GitHub or Apple either, and while that team requires SSO, people at its domain can sign in only with SSO. See Sign-In Methods and Your Account.

Team SSO domains must be verified by DNS and can't change while SSO is on, and expired team invitations no longer count toward seats. Raw HTML in Markdown and Contract questions is now limited to the formatting tags a question title allows: see HTML in Markdown.

Publishing via the API and MCP now runs the builder's checks

Released: September 27, 2026

POST /api/v1/forms/:id/publish and the MCP publish_form tool now use exactly the same publish pipeline as the Publish button. Team forms can only be published by team admins and owners, Pro features are checked against the form owner's plan, and booking, email-step, Fuse and composite questions must be fully configured. A blocked publish returns 409 Conflict with a reason and the question_ids to fix, and nothing is published. Successful publishes also record an audit-log entry, run content review, update open builders and return non-blocking warnings. Setting published on create or update now publishes through the same checks instead of switching the form live directly.

Unpublishing a team form through the API or MCP now also requires a team admin or owner, and the MCP server now applies the same per-user rate limits as the REST API. See Forms API and Error Handling.

Questionnaire Submit and Dynamic Choices

Released: September 27, 2026

Questionnaire-style forms now always show a Submit button. Answers save automatically while the respondent works, and Submit completes the response — so questionnaire responses now fire webhooks, send notification emails and count toward your response quota. Respondents then see the form's end screen — or a short confirmation when no end screen applies — with Submit another response (hidden when Limit to one response per visitor is on). A submitted response can't be edited, and an unfinished one resumes like on any other form. This replaces the old setting that locked answers after submission. Email steps now send when the form is submitted, and each data node gets a When to run setting: Keep up to date or Once, on submit. Phone calls are unchanged. See Questionnaire Style.

Multiple Choice, Dropdown, Ranking and Matrix questions (rows and columns) can now load their options from a variable, such as a data node's response: set Choice source to From a variable. Answers store each item's value and show its label in responses, exports and emails, and quiz scoring and conditions match the value. See Choices from a Variable.

NueLingo --- Auto-Translate on Demand

Released: September 17, 2026

Forms on the Pro plan can now be filled in in any of the 28 supported languages without translating them first. Turn on NueLingo in Form Settings → Languages: respondents pick their language (or arrive in it through browser detection) and each question is translated as they reach it, streamed in word by word, then saved to the form so the next respondent gets it instantly and you can edit it like any other translation. Your own translations always win. See Internationalization.

Change a Form's Default Language

Released: September 17, 2026

Any enabled language can now become the default: hover a language in Form Settings → Languages and click Make default. The form text swaps with the translation in place, the previous default is kept as a full translation, and the text-to-speech voice follows the new default.

February 2026

NueForm API v1 --- General Availability

Released: February 28, 2026

We are excited to announce the general availability of the NueForm REST API. The API gives you full programmatic access to forms, responses, webhooks, teams, and more.

API Endpoints

• Forms --- Create, read, update, delete, and publish forms via the API. Includes full support for all 25+ question types, logic jumps, variables, and theme configuration. See API Reference: Forms.

• Responses --- Retrieve form responses with filtering, pagination, and full answer data including quiz results. See API Reference: Responses.

• Webhooks --- Configure per-form and global webhooks programmatically. Manage your webhook secret for HMAC-SHA256 signature verification. See API Reference: Webhooks.

• Teams --- Create and manage teams, invite members, and assign roles. See API Reference: Teams.

• User --- Read and update account settings, manage API keys. See API Reference: User.

• Themes --- Configure form themes and branding defaults. See API Reference: Themes.

• Analytics --- Access form analytics and response metrics. See API Reference: Analytics.

• Files --- Upload and manage files used in forms. See API Reference: Files.

• Versions --- Manage form versions and publish history. See API Reference: Versions.

Authentication

API access uses Bearer token authentication with API keys. Keys follow the nf_<64 hex chars> format and can be generated in the Developer tab of your profile. See Authentication.

Rate Limits

• Pro plan: 100 requests per minute
• Enterprise plan: 500 requests per minute

See Rate Limits.

Webhooks

Real-time webhook notifications for form submissions. Features include:

• Per-form and global webhook URLs (up to 5 global webhooks)
• HMAC-SHA256 payload signing with the X-NueForm-Signature header
• form.submitted event with full answer data
• 5-second timeout, fire-and-forget delivery

See Webhooks Overview.

Documentation

Full documentation suite launched alongside the API:

• Getting Started --- Authentication, rate limits, errors, pagination
• API Reference --- Complete endpoint documentation
• Webhooks Guide --- Events, payloads, verification, testing
• User Guide --- Form builder and feature guides
• How-To Guides --- Step-by-step guides for common tasks

Plan Requirements

API access and webhooks require a Pro plan ($29/mo) or Enterprise plan ($99/mo). The Entrepreneur (free) plan does not include API access.