AFI
Fluent Forms
Fluent Forms is a fast, performance-focused WordPress form builder by the WPManageNinja team. Advanced Form Integration captures every Fluent Forms submission and routes the data to any of 200+ destinations.
What you’ll need
- The Fluent Forms plugin (Lite or Pro) installed and activated.
- The Advanced Form Integration plugin installed and activated.
- A form already built in Fluent Forms → All Forms.
Supported form fields
| Field type | Supported | Output format / notes |
|---|---|---|
| Single line text | Yes | Same as input |
| Yes | Same as input | |
| Phone | Yes | Same as input |
| Number | Yes | Same as input |
| URL | Yes | Same as input |
| Textarea | Yes | Same as input |
| Date / Time | Yes | YYYY-MM-DD, HH:MM |
| Select | Yes | The selected option |
| Multi-select | Yes | Comma-separated selected values |
| Radio | Yes | The selected option |
| Checkbox | Yes | Comma-separated selected values |
| Hidden | Yes | Same as the hidden value |
| Address | Yes | Each sub-field separately |
| Name | Yes | First / middle / last separately |
| File upload | Yes | Comma-separated public URL(s) |
| Image upload | Yes | Comma-separated public URL(s) |
| Rating | Yes | Numeric value |
| Net Promoter Score | Yes | Numeric 0-10 (Pro) |
| Repeater | Yes | JSON-encoded array of repeated rows (Pro) |
| Container / step | Not sent | Layout-only |
Create the integration
- Go to WP Admin → AFI → Add New.
- Enter an Integration Title.
- In Trigger → Form/Data Provider, select Fluent Forms.
- 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.
How AFI listens for submissions
AFI hooks into fluentform/submission_inserted, which fires after Fluent Forms validates and saves a submission. AFI runs after Fluent Forms’s own email notifications and integrations, so a submission that fails Fluent Forms validation never reaches AFI.
Multi-step forms
Fluent Forms’s multi-step forms fire AFI once after the final step submits. All field values are aggregated across steps in the payload.
Conditional logic example
Goal: route VIP-tier signups to Salesforce while standard signups flow only to Mailchimp.
Create two integrations on the same form. On the Salesforce integration, add a condition with the tier field, Equal To, value VIP. The Mailchimp integration stays unconditional.
Troubleshooting
Submissions not reaching the destination
Check AFI → Log for the most recent entry. Logs show the request payload and the destination’s response.
Form not appearing in the Form/Task Name dropdown
Re-save the form in Fluent Forms → All Forms to refresh the cache, then reload the AFI integration screen.
Repeater data is hard to map
Repeater fields arrive as JSON-encoded arrays. Most destinations don’t natively understand this. Either flatten before sending (use Zapier as an intermediary) or pick destinations that handle JSON natively.