Form or fields don’t appear in AFI’s dropdown

Estimated reading: 3 minutes

You go to create an integration, pick your sender plugin, and the form you just built isn’t in the dropdown — or the form is there but specific fields aren’t mappable.

Step 1 — Click the Refresh button

Next to the Form Name dropdown there’s a refresh icon. Click it. AFI re-fetches the form list from the sender plugin. This single step resolves a surprising number of tickets.

Step 2 — Submit the form once with sample data

Several sender plugins only persist a form’s field schema to the database on the first successful submission, not when you save the form in the editor. AFI reads the schema from the database, so until that first submission AFI sees nothing.

Plugins known to require this:

Avada Form — see Avada Form.
Forminator — mappings populate from saved entries.
Some Elementor Pro setups — particularly with conditional / hidden fields.

Open the form on the front end (or use the sender plugin’s preview), submit once with sample data, then refresh the AFI integration’s Form Name dropdown.

Step 3 — Confirm the form is published

Forms in draft status may not surface to AFI.
Forms that exist only inside an unpublished page may not register their schema in the right way.

Step 4 — Update AFI

Sender-plugin compatibility shifts over time. Recent fixes that affect form discovery:

Kadence Forms: recognition improved in v1.126.11.
Elementor Pro: “AFI option missing in Actions After Submit” fix in v1.114.6.
Ninja Forms: merge-tag format fix in v1.120.3.
WS Form: support added in recent versions.
Bricks Builder: support added in recent versions.

Step 5 — Form rename / rebuild

Form ID changes when you duplicate or recreate a form in some plugins (WS Form, Elementor — Elementor occasionally reuses internal IDs across forms). Your existing AFI integration may be tied to the old ID. Open the integration, re-pick the form, save.
Two forms with the same Elementor ID: use the form name to disambiguate; create one AFI integration per form.

Step 6 — Specific fields are missing

Free version only exposes text + email fields. Phone, date, dropdown, file, hidden, computed fields require AFI Pro.
Ninja Forms Name field must be the dedicated First Name / Last Name field type, not a generic text field.
Formidable Name field — same: use Formidable’s Name field type.
Elementor Pro Textarea — older versions missed it; update.
Custom field not detected (CF7, Elementor, Gravity Forms): use browser inspect, copy the input’s name attribute, wrap in {{...}}, paste into the mapping cell.