I’m running into an issue with handling multiple selection fields when connecting Typeform to Salesforce using Zapier.
My form has several options like:
Apple - Orange - Banana - Grape
These selections need to go into a text field in Salesforce. Right now when Zapier sends the data, it comes through as one long string:
AppleOrangeBananaGrape
This format is hard to read and looks messy. I tried adding commas in the Zapier template but when users don’t select all options, I get awkward results like:
Apple,Grape
What I really want is clean formatting like:
Apple, Grape
I’ve experimented with Zapier’s formatter tools but haven’t found a working solution yet. Has anyone dealt with this before and found a way to properly format multi-select values?
Had the same issue with our customer feedback forms. Skip the built-in formatters and use a JavaScript code step in Zapier instead. I wrote a simple script that splits the raw multi-choice data into an array, filters out empty values, and joins them back with commas and spaces. It handles all the edge cases without messy regex patterns. Just drop a Code by Zapier step between your Typeform trigger and Salesforce action, then use inputData.choices.split(',').filter(item => item.trim() !== '').join(', ') to clean up the formatting. Works perfectly across different form setups.
have u tried using zapier’s line itemizer? it helped me split multi-choice fields before and then you can format it back to a nice string with commas. worked great for my own typeform integration.
Had the same issue with our lead capture forms. Fixed it using Zapier’s Formatter with the Text action - specifically the “Replace” function to find empty selections and replace them with nothing. Set up a pattern that finds multiple consecutive commas and replaces them with single commas, then trim any leading/trailing commas. You can also use “Split Text” to break apart responses, then “Join” to put them back together with proper comma separation. This automatically eliminates empty values. The trick is preprocessing the data before it reaches Salesforce instead of fixing it later. Takes some trial and error to nail the regex patterns, but once you’ve got it configured, it handles all the edge cases perfectly.