How it works

Configured validation plus flexible extras

When Dynamic fields is enabled, configured fields are still validated normally. Additional keys are accepted, stored with the submission, included in CSV exports, forwarded to enabled webhooks, and added after configured fields in notification emails.

When it is disabled, unknown keys are rejected. Security fields such as the API key, honeypot, and captcha response are removed before storage and email delivery.

Naming fields

Use meaningful machine-safe keys

Use lowercase snake_case names. FormDex converts underscores, hyphens, and camelCase boundaries into readable email labels.

Submitted keyEmail label

company_nameCompany Name

project-budgetProject Budget

preferredCallTimePreferred Call Time

phone_numberPhone Number

Avoid generic keys such as field1 or data. They produce generic email labels and make exports harder to understand.

Notification email

Personalize the design with submitted values

Open the form, choose Settings, then open Notification email design. The variable reference lists every configured field. Copy a variable into the subject, header eyebrow, header title, introduction, tagline, watermark, footer, logo alt text, brand name, or brand tagline.

In the Brand tab, choose a full wordmark or an icon lockup, set a bounded logo size, and optionally place a brand name and tagline beside the icon. The Options tab can independently hide the logo, brand copy, eyebrow, title, header tagline, introduction, timestamp, and FormDex attribution. The live preview and delivered email use the same renderer.

Use {{form.name}} for the FormDex form name and {{field.field_name}} for a submitted value. The field name must exactly match the submitted JSON key or HTML input name. The older {formName} variable remains supported for existing templates.

Subject: New {{field.project_budget}} enquiry from {{field.full_name}}
Header title: {{field.company_name}}
Introduction: {{field.full_name}} submitted {{form.name}}. Reply to {{field.email}}.

Automatic details table
Configured and accepted dynamic fields are always rendered below the introduction. You do not need to add a variable for every field.

Missing optional values
A variable whose key was not submitted renders as blank. Design sentences so they still read clearly when an optional value is absent.

Values are inserted as text and HTML-escaped. Arrays and objects are compact when used in a variable and remain formatted JSON in the automatic details table. Email subjects are stripped of line breaks and control characters.

Examples

HTML form

<form action="https://YOUR_FORMDEX_DOMAIN/api/forms/FORM_ID" method="POST">
  <input name="full_name" value="Ada Lovelace" />
  <input name="company_name" value="Analytical Labs" />
  <input name="project_budget" value="₹50,000 – ₹1,00,000" />
  <textarea name="project_requirements">Website redesign and CRM integration</textarea>
  <button type="submit">Send enquiry</button>
</form>

JSON request body

{
  "full_name": "Ada Lovelace",
  "company_name": "Analytical Labs",
  "project_budget": "₹50,000 – ₹1,00,000",
  "project_requirements": "Website redesign and CRM integration"
}

These keys become Full Name, Company Name, Project Budget, and Project Requirements in the email. Send simple strings for the cleanest presentation. Arrays and objects are supported and displayed as formatted JSON.

Configured validation plus flexible extras

When it is disabled, unknown keys are rejected. Security fields such as the API key, honeypot, and captcha response are removed before storage and email delivery.

Use meaningful machine-safe keys

Use lowercase snake_case names. FormDex converts underscores, hyphens, and camelCase boundaries into readable email labels.

Submitted keyEmail label

company_nameCompany Name

project-budgetProject Budget

preferredCallTimePreferred Call Time

phone_numberPhone Number

Avoid generic keys such as field1 or data. They produce generic email labels and make exports harder to understand.

Personalize the design with submitted values

Subject: New {{field.project_budget}} enquiry from {{field.full_name}} Header title: {{field.company_name}} Introduction: {{field.full_name}} submitted {{form.name}}. Reply to {{field.email}}.

Automatic details table
Configured and accepted dynamic fields are always rendered below the introduction. You do not need to add a variable for every field.

Missing optional values
A variable whose key was not submitted renders as blank. Design sentences so they still read clearly when an optional value is absent.

HTML form

<form action="https://YOUR_FORMDEX_DOMAIN/api/forms/FORM_ID" method="POST"> <input name="full_name" value="Ada Lovelace" /> <input name="company_name" value="Analytical Labs" /> <input name="project_budget" value="₹50,000 – ₹1,00,000" /> <textarea name="project_requirements">Website redesign and CRM integration</textarea> <button type="submit">Send enquiry</button> </form>

JSON request body

{ "full_name": "Ada Lovelace", "company_name": "Analytical Labs", "project_budget": "₹50,000 – ₹1,00,000", "project_requirements": "Website redesign and CRM integration" }

Dynamic fields that stay readable.

Configured validation plus flexible extras

Use meaningful machine-safe keys

Personalize the design with submitted values

HTML form

JSON request body

Dynamic fields that stay readable.

Configured validation plus flexible extras

Use meaningful machine-safe keys

Personalize the design with submitted values

HTML form

JSON request body