JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Unable to submit Insightly CRM integrated formAsked by QualityTintingandSigns on September 21, 2016 at 05:05 PM
Hello I have a client form and I have set up an auto responder email to the customer who fills out the form. I have taken the email sender email off the bounce list, cleared the cache and tried having the sending email be a jot form email. This is driving me nuts. The test emails work fine too.
I have integrated the form to insightly via zapper. I have triggered insightly to create a contact every time a jot form is completed. The mapping of the fields went fine and the trigger is working however I keep getting an error message "
Oops! Insightly Integration Error! Field 'LAST_NAME' cannot be empty"
every time a form is filled out, screen shot attached. Its saying that the last name field is required. I am filling out the last name field and I have it mapped correctly. This is driving me nuts!
Insightly CRM Integration
The error is most likely related to the field mapping within your JotForm > Insightly CRM integration.
If you would like to use JotForm Insignthly CRM integration (instead of Zapier), I would like to suggest using a standard Full Name field for mapping.
Please give it a try and let us know if you need any further assistance.
That doesn't work because the insightly name fields are separated by
first name and last name. So when I do the mapping it looks like the
As far as I understand, the error is coming from our native Insightly CRM integration.
It should not be a problem to map the Full Name field in our integration.
I think that you will need to use either our integration or the integration via Zapier. In other words, please fix the fields mapping in our integration, or remove it completely to use your Zapier setup only.
I have moved your new question into a separate thread:
It will be updated shortly.