Tally form submission problem

CaraClyne

Member
Your Workflow URL
https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjcwNTZkMDYzNTA0MzA1MjZhNTUzYzUxMzIi_pc
Your Task History ID
IjU3NjUwNTY1...
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
Pabbly → Flodesk: Multi-choice field sends all options instead of the selected one (can’t tag correctly)


Hi team I’m using Pabbly Connect to send a Tally submission into Flodesk so I can save the subscriber and apply a segment/tag based on a multiple-choice answer.

Problem:
In the Pabbly form submission payload, the multiple-choice field is not coming through as the single selected value. Instead, it’s coming through as every possible option (the entire list), so I can’t reliably map the chosen answer and apply the correct Flodesk tag.
 

Hrishabh.pabbly

Member
Staff member
Hello,

Thank you for reporting this. We checked the webhook response coming from Tally, and we can confirm that Tally is sending only the selected option, but it sends it in the form of an option ID, not the option text.

What Tally sends in the webhook​


For every Multiple-Choice field, Tally provides:
  • value → this contains only the ID of the selected option
  • options → this contains the full list of all options (with ID + text)

So the selected answer is inside the webhook, but we need to match the selected ID with the correct text label.

1765516109687.png


To help you correctly extract the selected option, we need to review the webhook structure from your account.

Could you please recapture the Tally webhook response using “Advanced Format” in Pabbly Connect?

1765516143014.png


This will give us the complete structured payload, and we can guide you exactly how to extract the chosen option text for tagging inside Flodesk.
 
Top