WPForms

Estimated reading: 3 minutes Updated August 1, 2026

WPForms is one of the most-installed WordPress form plugins, with over 6 million active installs across the free and Pro versions. Advanced Form Integration captures every WPForms submission and routes the data to any of 200+ destinations.

What you’ll need

The WPForms plugin (Lite or Pro) installed and activated.
The Advanced Form Integration plugin installed and activated.
A form already built in WPForms → Add New.

Supported form fields

Field type	Supported	Output format / notes
Single line text	Yes	Same as input
Email	Yes	Same as input
Phone	Yes	Same as input
Numbers	Yes	Same as input
Number slider	Yes	Numeric value
Website / URL	Yes	Same as input
Paragraph text	Yes	Same as input, line breaks preserved
Date / Time	Yes	`YYYY-MM-DD` and `HH:MM`
Dropdown	Yes	Selected value, comma-separated for multi-select
Multiple choice	Yes	The selected option label
Checkboxes	Yes	Comma-separated selected values
Name	Yes	First / middle / last each map separately
Address	Yes	Each sub-field maps separately
Hidden	Yes	Same as the hidden value
File upload	Yes	Comma-separated public URL(s)
Rating	Yes	Numeric value
Signature	Yes	URL of the signature image (Pro)
Net Promoter Score	Yes	Numeric 0-10 (Pro)
Likert scale	Yes	Each row’s selected value (Pro)
Rich text	Yes	HTML body (Pro)

Create the integration

Go to WP Admin → AFI → Add New.
Enter an Integration Title, e.g. WPForms contact → HubSpot.
In Trigger → Form/Data Provider, select WPForms.
In Form/Task Name, choose the form to listen on.
In Action → Platform, pick the destination and complete the field mapping.
Optional: configure Conditional Logic.
Click Save Integration.

Screenshot: AFI Add New screen with WPForms selected as the Form Provider, showing the Form/Task Name dropdown listing WPForms by name

How AFI listens for submissions

AFI hooks into wpforms_process_complete, which fires after WPForms validates and saves a submission to the database. AFI runs after WPForms’s own email notifications and entry storage, so a submission that fails WPForms validation never reaches AFI.

Multi-page forms

WPForms multi-page forms (Pro feature) fire AFI once after the final page submits. Earlier page transitions don’t fire individual events. All field values are collected and sent in a single payload.

Conditional logic example

Goal: when a contact form’s Department dropdown is Sales, route to your sales CRM. Other departments go to a shared support inbox via a separate integration.

Create two integrations on the same form. On the sales CRM integration, open the Conditional Logic panel, add a condition with the department field, Equal To, value Sales. On the support integration, use Not Equal To Sales.

File uploads

WPForms uploads land in /wp-content/uploads/wpforms/ by default and get a public URL. AFI sends that URL string to the destination. If you want files to land in a private location, configure WPForms to use the WordPress media library, or pair with a plugin that uploads to S3/Dropbox before AFI fires.

Troubleshooting

Submissions not reaching the destination

Open AFI → Log and find the most recent entry. The log shows the exact request payload and the response from the destination, usually pointing straight at the cause.

Form not appearing in the Form/Task Name dropdown

WPForms caches form metadata. Re-save the form in WPForms → All Forms to refresh, then reload the AFI integration screen.

Smart tags don’t resolve

WPForms-specific smart tags like {user_ip} or {page_title} are evaluated by WPForms before the data reaches AFI. If you need them in your destination, ensure they’re enabled in the WPForms field’s “default value” or notification settings.