Publishing & Sharing

Overview

Publishing is the process of making your form available to respondents. NueForm uses a versioned publishing system that lets you make changes to your form without affecting the live version until you are ready.

Publishing Workflow

Draft vs. Published

Every form exists in two states:

• Draft: The version you see and edit in the form builder. Changes are saved automatically but are not visible to respondents.
• Published: The version that respondents see when they visit your form URL. This is a snapshot of the form at the time you clicked Publish.

When you make changes to a published form, the builder shows a badge indicating unpublished changes. Respondents continue to see the previously published version until you publish again.

How to Publish

1. Open your form in the builder.
2. Make your desired changes.
3. Click the Publish button in the top-right corner.
4. Your changes are now live.

Versioning

NueForm automatically creates a version snapshot each time you publish. This gives you a complete history of your form over time.

Version Details

Each version records:

Change Tracking

NueForm automatically tracks changes between publishes:

• Questions added, removed, or reordered
• Question text, type, or settings changed
• Form settings modified (theme, title, mode, etc.)
• Logic jumps added or modified

These changes are compiled into a changelog that is stored with each published version.

Reverting to a Previous Version

If you need to go back to an earlier version of your form:

1. Navigate to the form's version history.
2. Select the version you want to restore.
3. Click Revert to this version.

Sharing Your Form

Public URL

Every published form is available at:

https://nueform.io/f/{slug}

Where {slug} is your form's unique identifier. For example:

https://nueform.io/f/customer-feedback-2024

Custom Slugs

You can customize your form's slug to make the URL more memorable:

1. Open your form settings.
2. Find the Slug field.
3. Enter your desired slug (lowercase letters, numbers, and hyphens only).
4. Save.

Custom Domains

With a Pro+ plan, you can serve your forms from your own domain:

• Subdomain: yourcompany.nueform.io/f/{slug}
• Custom domain: forms.yourcompany.com/f/{slug}

See the Custom Domains guide for setup instructions.

URL Parameters

You can pass data to your form through URL parameters. These become available as URL variables for use in logic jumps and text substitution:

https://nueform.io/f/my-form?name=John&source=email

In this example, {name} would resolve to "John" and {source} would resolve to "email" anywhere in your form's titles, descriptions, or logic conditions.

See the Variables guide for more details.

Embedding

You can embed your form on any website using an iframe:

<iframe
  src="https://nueform.io/f/{slug}"
  width="100%"
  height="600"
  frameborder="0"
  style="border: none;"
></iframe>

Passing URL Variables in Embeds

You can pass URL variables to embedded forms just as you would with direct links:

<iframe
  src="https://nueform.io/f/my-form?name=John&company=Acme"
  width="100%"
  height="600"
  frameborder="0"
></iframe>

Webhooks

With a Pro+ plan, you can configure a webhook URL on your form. When a response is submitted, NueForm will send a POST request to your webhook URL with the response data.

Webhook Payload

The webhook POST body includes:

• L'identifiant du formulaire
• L'identifiant de la réponse
• All answers
• Quiz results (if applicable)
• Submission timestamp
• Visitor ID (if available)

Webhook Security

You can configure a webhook secret in your account settings. When set, all webhook requests include an HMAC-SHA256 signature in the request headers that you can use to verify the request came from NueForm.

Global Webhooks

In addition to per-form webhooks, you can configure up to 5 global webhooks in your account settings. Global webhooks fire for every form submission across all your forms.

Incremental Submission

When enabled, NueForm saves partial responses as the respondent progresses through the form. This means:

• If a respondent abandons the form partway through, you still have their partial answers.
• Each time the respondent advances to the next question, their progress is saved.
• The response is marked as "completed" when they reach the end and submit.

This is especially useful for long forms where drop-off is a concern.

Limiting Responses

The Limit One Response setting uses browser-based visitor identification to prevent the same person from submitting the form more than once. When enabled:

• A unique visitor ID is generated and stored in the browser's local storage.
• On subsequent visits, the form checks whether this visitor has already submitted.
• If they have, the form displays a message instead of allowing a new submission.