Skip to content
  • There are no suggestions because the search field is empty.

How to convert Firmable's text values into your CRM's picklist fields

Learn the general approach for mapping a Firmable text value onto a picklist, dropdown, or choice field in your CRM, so pushes don't fail on a mismatch.

Why this is needed

Firmable pushes field values as plain text. Many CRM fields, industry, company size band, lead source, and similar, can be picklist, dropdown, or choice fields with a fixed set of allowed values. If the text Firmable sends doesn't exactly match one of those allowed values, the push can fail for that field, or in some CRMs, fail the entire record.

This isn't specific to one CRM, the same underlying problem shows up on Salesforce, Dynamics, HubSpot, and Pipedrive, wherever the target field is picklist-type rather than free text.

The general approach

The fix is the same shape regardless of CRM: intercept the value before it lands in the picklist field, and map it to one of the field's allowed options.

Step 1: Identify every mismatched field

  • List the exact allowed values for each picklist field Firmable pushes into. Most CRMs let you export or view this from the field's setup page.
  • Compare that list against the actual text values Firmable sends for that field. Anywhere they don't match exactly (including casing and punctuation) is a field that needs conversion.

Step 2: Build a mapping table

  • For each mismatched field, build a simple lookup, Firmable's value on one side, the CRM's matching allowed value on the other.
  • Decide what happens when a Firmable value has no match at all, either map it to a sensible default (for example "Other"), or leave the field blank rather than blocking the whole push.

Step 3: Apply the mapping using your CRM's automation tool

  • Salesforce: a Flow (or a formula field) that reads the incoming text value and assigns the matching picklist value
  • Dynamics 365: a Power Automate flow, using a Switch or a lookup table action to convert the value before the Update/Add a row step
  • HubSpot: a workflow with branching logic, or a calculated property that translates the value
  • Pipedrive: a custom field with predefined options, paired with a Zapier/Make/n8n step doing the same lookup, since Pipedrive doesn't have a native workflow builder for this

Step 4: Run the conversion before the picklist field is set

  • Make sure the mapping step runs ahead of the create/update action, not after, most of these tools let you insert a transform step before the final write.

Step 5: Test with a single record first

  • Push one test record covering a value you know needs conversion, and confirm it lands as the correct picklist option, not blank or rejected.
  • Only then run it against a larger batch.

Frequently asked questions

  • Do I need to rebuild this for every CRM I use? The mapping table and the general approach stay the same, only the tool you use to apply it changes, see step 3 for the CRM you're on.

  • What happens if I don't fix this? The affected field is usually left blank on the pushed record, or in some CRMs, the whole record is rejected if the picklist field is mandatory. It can look like a Firmable sync failure when it's actually a mapping mismatch.

  • Can I avoid this altogether? Only if every target field in your CRM is free text rather than picklist. For fields tied to reporting or automation elsewhere in the CRM, mapping is usually the better option than converting them to text.

We hope this article has helped you handle text-to-picklist mismatches in your CRM. If you have any other questions, don't hesitate to contact us at support@firmable.com.