Skip to main content
Question

Difficulty Mapping Duplicate-Labeled Fields from Elfsight Form Submission into GorillaDesk CRM

  • January 14, 2026
  • 3 replies
  • 12 views

Hi Zapier Community,

When I made my Zap live and submitted a new submission from my connected Elfsight form, Zapier was able to differentiate between the fields that share the same label in the output. However, all of the fields came through jumbled in GorillaDesk (my CRM software). This appears to be because, during the Zap setup, there is no way for me to tell which field is which. In the editor, the fields are displayed with identical names and do not show the unique Field ID, nor are they listed in the order they appear in my form, so I cannot map them correctly—even though the live submission shows that they are distinct in the backend. The AI assistant is unable to do it either as it appears it too cannot differentiate between them.

In other words, the form works correctly once it’s live, but the setup process itself is extremely difficult to complete because I cannot identify which duplicate-labeled field corresponds to which one in the Zap editor. See accompanying screenshots attached showing the issue.

For reference, the four addresses I submitted in the Elfsight form test submission were:

  • 1 Test Street, Test Address Line 1, Suburb1 State1 5001 – Daycare 1 – Owned by us 1
  • 2 Test Street, Test Address Line 2, Suburb2 State2 5002 – Daycare 2 – Owned by us 2
  • 3 Test Street, Test Address Line 3, Suburb3 State3 5003 – Daycare 3 – Owned by us 3
  • Billing Address: B Test Street, Test Address Line B, SuburbB StateB 5004

Do you have any suggestions on how I can correctly configure the Zap when I’m unable to differentiate between fields that share the same label during setup? I’m on the free Zapier plan, FYI.

Thank you for any assistance you can provide.

3 replies

drtanvisachar
Forum|alt.badge.img+2

Hello ​@K9 Pooper Troopers 

This happens when your form sends multiple fields with the same label. Zapier can read them in live runs, but in the setup screen it can’t tell which is which.

Best fix: rename the fields in Elfsight so each one is unique, like “Service Address 1 Street”, “Service Address 2 Street”, “Billing Street”.

If you can, add a hidden field like “Address Type” or “Address Number” to help identify each group.

On the Free plan, changing the labels is the simplest solution.


Dr. Tanvi Sachar
Monday Certified Partner, Monday Wizard


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • January 14, 2026

Hi ​@K9 Pooper Troopers 

Issue may be related to repeated sections in Elfsight.

If you can rename the fields to each be unique, then that should help you be able to configure the Zap action steps.

 

For more advanced handling of the data from Elfsight, that would require more Zap steps, which requires a Zapier paid plan to be able to turn the Zap ON.

 

If you are looking to hire help, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory


Hi ​@drtanvisachar and ​@Troy Tessalone,

Thanks for your insights! I just wanted to clarify—if I were to upgrade to a paid Zapier plan, would that allow me to differentiate between fields that have identical labels but unique field IDs in the backend? In other words, would the Zap editor display them in a way that lets me map them correctly without having to rename all the fields in Elfsight?

Appreciate any clarification.

Thanks,
Michael