Integrations
Connect Gravity Forms so its submissions become contacts or leads in FlyCRM.
This page covers what is specific to Gravity Forms. The shared steps (field mapping, duplicate handling, and defaults) are in Capturing leads from forms.
Install and activate Gravity Forms. Until it is active, the FlyCRM integration stays turned off.
You also need at least one Gravity 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.
Gravity Forms has fields that hold several parts, such as Name and Address. FlyCRM splits them, so each part appears as its own row in the mapping table.
For a name field, map the parts you need:
| CRM field | Form field |
|---|---|
| First Name | Name (First) |
| Last Name | Name (Last) |
Use the Full Name row only for a single text field that holds the whole name.
The list holds data fields only. HTML blocks, sections, page breaks, and CAPTCHA fields do not appear, because there is nothing in them to map.
An Address field also splits into parts, such as street, city, and postal code. Map only the parts you need. FlyCRM has no address fields of its own, so most forms leave these unmapped and keep the address in the logged activity instead.
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 Gravity Forms saves the entry. 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.