Integrations
Connect Ninja Forms so its submissions become contacts or leads in FlyCRM.
This page covers what is specific to Ninja Forms. The shared steps (field mapping, duplicate handling, and defaults) are in Capturing leads from forms.
Install and activate Ninja Forms. Until it is active, the FlyCRM integration stays turned off.
You also need at least one Ninja 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.
Ninja Forms shows each field by its label. A field labeled Your Email appears as Your Email in the mapping table.
The list holds data fields only. Buttons, HTML blocks, and dividers do not appear, because there is nothing in them to map.
A Ninja Forms contact form usually has a name, an email, a phone, and a message. 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.
Most Ninja Forms forms use one field for the whole name. Map that field to Full Name. FlyCRM splits it: the last word becomes the last name, and the rest becomes the first name.
If your form has two separate fields, map them to First Name and Last Name 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 Ninja Forms processes 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.