Integrations
Connect Fluent Forms so its submissions become contacts or leads in FlyCRM.
This page covers what is specific to Fluent Forms. The shared steps (field mapping, duplicate handling, and defaults) are in Capturing leads from forms.
Install and activate Fluent Forms. Until it is active, the FlyCRM integration stays turned off.
You also need at least one published Fluent Forms 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.
FlyCRM lists your published forms under Form. A draft form does not appear until you publish it.
The Fluent Forms Name field holds first, last, and middle name together. FlyCRM splits it, so each part appears as its own row in the mapping table.
Map each part to the matching CRM field:
| CRM field | Form field |
|---|---|
| First Name | Name (First Name) |
| Last Name | Name (Last Name) |
You do not need the Full Name row for a Fluent Forms name field. Use Full Name only for a plain, single text field that holds the whole name.
Fluent Forms groups some fields, such as Address, into several parts. FlyCRM flattens these, so each part is available on its own. Map only the parts you need, and leave the rest unmapped.
Map single-value fields, such as 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 Fluent Forms saves 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.