• Automatic tag parsing: Upload a .docx template and the plugin extracts every merge tag, conditional block, and loop structure it contains.
• Intelligent field type inference: The plugin analyses tag names and their context to suggest the most appropriate Gravity Forms field type — email addresses become email fields, dates become date pickers, phone numbers become phone fields, and so on.
• Condition-aware typing: Fields used in equality conditions (e.g., {% if Status == "Approved" %}content{% endif %}) are detected as radio buttons or dropdowns, with the tested values pre-populated as choices.
• Confidence indicators: Each suggested field type shows a confidence level (high, medium, low) so you can see which inferences are reliable and which are best guesses.
• Editable review table: Before creating the form, review all detected fields in a table. Include or exclude fields, change field types, and mark fields as required.
• List field detection: Repeating structures (for/endfor loops) are identified and mapped to Gravity Forms List fields with the correct column configuration.
• Conditions summary: All conditional rules found in the template are listed so you can see the logic the template expects.
• One-click form creation: Creates a complete Gravity Forms form via the GF API with fields typed, labelled, and configured.
• Non-destructive: Each run creates a new form. It never modifies or overwrites existing forms.
• No AI or API key required: Template to Form uses deterministic parsing, i.e., no API calls. It runs entirely locally in your WordPress installation.

Do I need GravityMerge AI to use Template to Form?

Gravity Forms is required (for form creation via the API). The forms Template to Form creates are designed to work with GravityMerge AI templates and so, yes, for all practical purposes you need GravityMerge AI. 

Do I need an API key?

No. Template to Form uses rule-based parsing, not AI. No API calls are made.

What merge tag format does it recognise?

GravityMerge AI merge tags: {{ field_name }} for basic tags, {% if %} / {% endif %} for conditionals, and {% for %} / {% endfor %} for loops.

How does it know what field type to use?

The plugin applies a set of naming rules and contextual analysis. For example, a tag named "Email address" maps to an email field. A tag named "Start date" maps to a date picker. A tag used in a condition like {% if Country == "New Zealand" %} becomes a dropdown with "New Zealand" as one of the choices. You can override any suggestion before creating the form.

Can I run it multiple times on the same template?

Yes. Each run creates a new form, so you can experiment freely.

Does it handle list/repeater fields?

Yes. Loop structures in the template are detected and mapped to Gravity Forms List fields with the appropriate columns.

What if the plugin guesses a field type incorrectly?

Change it in the review table before creating the form (every suggestion is editable) or change it in the form once created.