Zapier Integration: Fields mapping is hard to use

  • travisfoote
    Asked on September 1, 2018 at 2:24 PM

    In the forms I have created, Jotform is not using the Unique Field name I provide.  For example I have a form field that has a unique name of userName.  When the value is stored in Jotform, it uses the value of the field Header text to store the field's value and not the unique name.


  • Adrian
    Replied on September 1, 2018 at 2:33 PM

    I apologize but I am not sure if I understand you correctly.

    I can see that you have a Full Name field in your form that has the unique name userName.

    Zapier Integration: Fields mapping is hard to use Image 10

    I have made a test submission to your form and everything seems to be working properly.

    If you want to extract the First name or the Last name (in Emails or URL parameters), you can use the following expressions.

    {userName:first} - (for the First Name)
    {userName:last} - (for the Last Name)

    Let us know if you need further assistance.

  • travisfoote
    Replied on September 1, 2018 at 2:43 PM
    Ok.
    The issue is that Jotform is not using the Unique Name of userName to store the value in the spreadsheet Jotform saves the form submissions into. It also does not use the Unique Name in the email sent. Nor does it use the Unique name when trying to integrate the form with Zapier
    See below. The unique names are not used here
    ...
  • Mike_G JotForm Support
    Replied on September 1, 2018 at 3:18 PM

    I see that you are trying to show us a screenshot of the issue. However, I would like to apologize, but the screenshot was not posted. To include a screenshot in your reply, please follow the instructions in this guide — How-to-Post-Screenshots-to-Our-Support-Forum

    As for your concern, the unique name you set will not be the one showing in the spreadsheet your form is integrated with nor the field name that will show when you try to integrate with Zapier because it is not meant for those. The unique name is used to extract the value of a field if you want to pass it to another form, prepopulate fields from the URL, or show the value of a field in the emails, thank-you page, and/or text (HTML) field.

  • travisfoote
    Replied on September 1, 2018 at 3:43 PM
    See below a screen shot of how the fields are named when using this Jotform with Zapier. They are not named with the Unique names field.
    In the screen shot below, the fields_Name should be called fields_userName and not fields_Name
    ...
  • travisfoote
    Replied on September 1, 2018 at 3:43 PM
    I just tested the following. I changed the value of the Question Text for the userName field to User Name. Then I submitted the form again. In Zapier the field name changed to fields_User Name. Again not using the Unique Name property of the field, instead using the Question Text value. Because its using the Question Text value (and similar field properties for other fields), this is making it extremely difficult to map values for fields for integration. If Jotform were using the unique name parameter of the field, then we would know what how to find each field when integrating and map them easily.
    ...
  • Mike_G JotForm Support
    Replied on September 1, 2018 at 4:23 PM

    We would like to apologize for any inconvenience. However, it is not the Unique Name that's being used during integration but the Field Name/Field Label/Question Text.

    Unless the fields in your form have similar Field Name/Field Label/Question Text, then integrating your form with Zapier should not be difficult.

    Again, the UniqueName is used for specific things that I have already mentioned above.

    We can submit a feature request on your behalf to our developers so there will be an option to choose between the Unique Name and Question Text to use during integration but, there is no guarantee that it will be implemented anytime soon.

    There is a workaround using CSS codes if you want to use a specific Question Text in your form fields for the integration but you would like to show a different field label on the form. Just let us know and we will be glad to help you with that.

  • travisfoote
    Replied on September 1, 2018 at 6:43 PM
    yes please share the css work around. there are several form fields that
    have the same names
    ...
  • Mike
    Replied on September 1, 2018 at 11:04 PM

    Here is an example:

    1) Set the Question Text. It will be displayed in Zapier.

    Zapier Integration: Fields mapping is hard to use Image 1 Screenshot 40

    2) Check the field ID using the browser developer tools.

    Zapier Integration: Fields mapping is hard to use Image 2 Screenshot 51

    3) Use the field ID in a custom CSS to display a different "label":

    #id_8 .form-label {
    font-size: 0;
    }
    #id_8 .form-label:before {
    content: "Name";
    font-size: 14px;
    }

    Zapier Integration: Fields mapping is hard to use Image 3 Screenshot 62

    We have also raised a ticket to see if the naming can be improved in Zapier. There is no ETA, but we will let you know if we have any updates on this.

  • travisfoote
    Replied on September 2, 2018 at 10:43 AM
    Interesting work around. So I would give the label a name that is unique and use CSS to change what is displayed. Ok I’ll give it a try. Will this also rename the fields in the spreadsheet Jotform populates?
    IMO the feature request maybe needed for both Jotform and its integration partners. Since Jotform is not using the unique name field when it stores the fields values in the spreadsheet either. I currently am using the integration with Google Sheets and it also is not using the unique name field.
    ...
  • travisfoote
    Replied on September 2, 2018 at 10:43 AM
    It does rename the column header in the spreadsheet as well.
    ...
  • Mike
    Replied on September 2, 2018 at 11:56 AM

    Thank you for your input. We will consider this, but this is not likely that the format of the Google Sheet headings will be updated in the nearest time. We will let you know if we have any updates on the Zapier issue.