I wish to map a series of “Yes” / “No” radio fields in a Squarespace form to a corresponding set of custom single option fields (under the Person tab) in Pipedrive whose option values are also explicitly “Yes” / “No”. The option values match exactly in terms of case in both systems. I am getting NO values for the fields in Pipedrive upon submission of the Squarespace form, nor do I see any complaints from the Zap. I tried setting the same fields in Pipedrive to text types thinking that there may be some issue with the literal values not matching exactly, but still no luck. Thanks for any assistance with this!
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.
+14- Zapier Orchestrator & Solution Partner
- 34072 replies
Hi
Check this help article for the expected values to use in dropdown fields:
Thank you, Troy. I think my issue is simpler. (My use of “custom” field may have created the confusion.) I just want to map “Yes” and “No” values in an option field in a Squarespace form to “Yes” and “No” values in a single option data field in Pipedrive. The field mapping appears correct in my zap, but I’m either getting no values when I submit the Squarespace form, or if I select static values in my Zap mapping I simply get those same values every time, regardless of the actual values selected in the Squarespace form. What am I missing here?
+14- Zapier Orchestrator & Solution Partner
- 34072 replies
Post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings visible so we can see the field types and field options for dropdown fields.
A couple more screenshots… one is an example Squarespace data field definition, the other the corresponding data field in Pipedrive.
+14- Zapier Orchestrator & Solution Partner
- 34072 replies
NOTE: Make sure to test your Zap trigger step to get real data instead of dummy data.
Click the [...] button to change to “Custom” mode, so you can map variables.
Troy:
I’ve done the mapping (see attached screenshot) but I’m seeing “Option One” as the data value. This is creating an error when testing the Pipedrive step (see attached screenshot).
Thanks.
+14- Zapier Orchestrator & Solution Partner
- 34072 replies
The error is due to trying to test with dummy data from Zap step 1.
Try turning your Zap ON and testing live.
Then check your Zap Runs history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/
Troy:
Thanks for all your help. I’ve had a successful run using a live test, plus I had to change the Pipedrive data field types to text… the radio button to radio button mapping was just not working. Again, thanks!
+6- Zapier Staff
- 6780 replies
Hi there
For the Radio Buttons field, you'll need to provide the specific ID associated with each option. If you hover over the “Yes” or “No” options in the Pipedrive step, you should be able to see the required ID. You might want to utilize Lookup Table for the dynamic mapping of radio buttons to work.
You can learn more about the Lookup Table here:
Hopefully, this helps!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.