Integrations
Connect WPForms so its submissions become contacts or leads in FlyCRM.
This page covers what is specific to WPForms. The shared steps (field mapping, duplicate handling, and defaults) are in Capturing leads using forms.
Install and activate WPForms. Both WPForms Lite and the paid versions work with FlyCRM. Until WPForms is active, the FlyCRM integration stays turned off.
You also need at least one WPForms form that collects an email address. FlyCRM uses the email to tell a new person from a returning one, so a form without an email field cannot feed the CRM.
WPForms shows each field by the label you gave it in the form builder. A field labeled Email Address appears as Email Address in the mapping table.
The list holds data fields only. Layout parts, such as section dividers, page breaks, and HTML blocks, do not appear, because there is nothing in them to map.
A WPForms contact form usually has a Name field, an Email field, and a Comment or Message field. Map it like this:
| CRM field | Form field |
|---|---|
| Full Name | Name |
| Phone | Phone |
Leave the message field unmapped. To keep the message, turn on Log form submission as activity in the feed. FlyCRM then saves the whole submission as a note on the record.
The WPForms Name field holds the full name in one place. Map it to Full Name. FlyCRM splits it: the last word becomes the last name, and the rest becomes the first name.
If your form uses two separate fields for the name, map them to First Name and Last Name instead.
Map single-value fields, such as single-line text, email, and phone. A checkbox field or a multi-select field can hold several values, so it does not fit one CRM field.
To keep those answers, turn on Log form submission as activity. FlyCRM lists every submitted field in the note, and joins multiple values with commas.
FlyCRM captures the submission after WPForms finishes processing it. FlyCRM also records the page the form was submitted on. For leads, it reads any UTM parameters in that page's URL. You do not map these values.