FORM INTELLIGENCE, EXPLAINED.
FormLint for Gravity Forms
Give your Gravity Forms an extra layer of understanding. Manage your intelligence without rebuilding your form.
One WordPress plugin. Your existing forms.
WordPress plugin. Download includes installation instructions and license notices. These packages are distributed directly by FormLint; no platform endorsement or marketplace approval is claimed.
Download Gravity Forms integrationRequires WordPress 6.5+, PHP 8+ and Gravity Forms. The same ZIP supports both builders. Test your installed builder version on staging before use.
- Upload the ZIP.In WordPress, open Plugins → Add New → Upload Plugin. Select the downloaded ZIP, install and activate it.
- Open Settings → FormLint.Select Gravity Forms, enter the evaluation endpoint and your project public key. Missing builders stay inactive.
- Enable the connection.Complete the mapping below, check Enable processing, and save. Suggestions appear below mapped fields after visitors edit them.
Match your fields. Keep their native names.
Create or choose your FormLint project, save its rules and field IDs, and create a public key. Use your HTTPS evaluation endpoint ending in /evaluate. Keep provider and server secrets out of every plugin.
Add the exact origin where the form runs to the project’s allowed origins. Include your staging origin separately when testing.
| Setting | Example | Where to find it |
|---|---|---|
| Form ID | 12 | The numeric form ID in Gravity Forms. |
| Project field ID | description | The field saved in your FormLint project. |
| Builder field ID | 3 | The numeric field ID in the form editor. |
This maps input_3 to description for suggestions. The native name and submission remain intact. A single checkbox subinput can use a field ID such as 3.1. Grouped choices are excluded.
Your rules live in FormLint.
Write your checks and visitor messages in the project and save. For a packaging brief, check quantity and dimensions with separate rules, each with its own suggestion. For quantity, use “Add how many items you need.” Learn how to write useful rules.
Map up to four non-sensitive fields, at most 4,000 characters each: native textarea, text, number, single select or individual checkbox. Files, custom choice widgets, grouped controls and sensitive input types are excluded. The integration does not read browser storage or keep answers across form pages; use rules whose mapped fields appear together.
Widget language
Choose Auto, English or Italiano in the integration settings. Auto follows the form document’s HTML language, including runtime changes. Add all rule translations and choose the default language in FormLint’s Form setup. Missing or unsupported translations use the project default for every message.
If your custom switcher does not update the page’s HTML language, call setLocale on the integration instance. Switching existing feedback does not consume another evaluation. Language setup and SDK examples.
Test the whole form.
- Confirm feedback is hidden on load and appears below the mapped field after an edit.
- Try incomplete and complete synthetic examples. Simulated mode recognizes supported fixtures only; arbitrary text can return unavailable.
- Check that the selector matches exactly one form and each mapped selector one supported input. Missing suggestions usually mean a mapping, origin, key or endpoint mismatch.
- Test AJAX refreshes, popups and navigation. Replaced inputs reconnect; previous requests are discarded.
- Disable the evaluation endpoint and submit. The original submission must still work.
To disconnect, uncheck the connection and save, or deactivate the plugin. Clear page caches after changes. Uninstall removes only the current site’s FormLint settings.