Thread Discussion

1. country (a text field)
2. cocoroco_languages (a multi-select checkbox field, which provides a semicolon-separated string like en;de)

• When I test the failing deals manually using the "Test" feature in the workflow editor, the code runs successfully and updates the rate.
• The issue only occurs during automatic enrollment.
• The workflow logs for the failing deals show that the function is being triggered and the input data (country and cocoroco_languages) is being received correctly. However, the code fails to find a match for the country in the rate table, even though the logged country name (e.g., 'Spain') appears to be an exact match to a key in my rate table object.

1. Workflow Triggers: The workflow enrollment and re-enrollment triggers are set up correctly. The action runs for every deal as expected.
2. Permissions: The Private App has the necessary crm.objects.deals.write and crm.objects.deals.readscopes.
3. Empty Data: The workflow has filters to ensure that country and cocoroco_languages have known values before the code action runs. The logs confirm these values are present.

// Input from the workflow action
const countryInput = event.inputFields['country'] || '';

// My current attempt at cleaning the data
const country = countryInput.replace(/\s/g, ' ').trim();

// ... logic to determine workingLangName ...

// The lookup logic
const countryKey = Object.keys(hourlyRates).find(
  c => c.toLowerCase() === country.toLowerCase()
);

if (countryKey) {
  // ... find rate based on language
} else {
  // This is the log message I see for failing deals
  console.log(`Result: No rate found. Country '${country}' is not in the rate table.`);
}

1. Has anyone else experienced this kind of intermittent failure with custom code actions, where it points to hidden characters in property values?
2. What is considered the "best practice" for robustly sanitizing string inputs from HubSpot properties within a serverless function to avoid this exact problem? Is my .replace(/\s/g, ' ') approach sufficient, or is there a more foolproof method?