Why does .toTitleCase convert 'IN PERSON' to 'in Person'?

Below is a few ideas to troubleshoot and work around the issue:

1. Check for extra characters or whitespace:
   Sometimes, the input may include leading/trailing spaces or hidden characters that affect the first character’s transformation. Use a trim operation first. For example:

   JSCopied
   const input = $json.yourField.trim(); 

2. Verify the transformation logic:
   The built‐in .toTitleCase function should capitalize the first character of each word. In most cases it’s implemented roughly as follows:

   JSCopied
   const toTitleCase = str =>
     str.toLowerCase().replace(/\b\w/g, txt => txt.toUpperCase());
     
   const result = toTitleCase(input);

   In your case, if “IN PERSON” becomes “in Person”, it suggests that the first letter isn’t getting the uppercase treatment, perhaps because it’s not the first non‑whitespace character or the regex isn’t matching as expected. You might try a custom code node with the snippet above to see if that forces “In Person.”

3. Consider potential differences in node behavior:
   Since you mentioned that every other instance using .toTitleCase works fine, it could be that this particular input from Google Calendar has some quirk (for example, a hidden character or an extra space) that causes the first letter “I” not to be recognized properly by the regex. Logging the raw output (for example, using a Set node to output a JSON property) might help confirm whether there’s an unseen character.

4. Apply a manual fix if needed:
   If the first character still isn’t capitalized because of the library’s behavior, you can force capitalization manually. For example:

   JSCopied
   let title = toTitleCase(input);
   // Force uppercase first letter if still lowercase
   title = title.charAt(0).toUpperCase() + title.slice(1);
   return { title };

By trimming the input and using a custom function to perform title-case conversion, you should be able to achieve the expected “In Person” result. If the problem persists, double-check the exact content coming from Google Calendar, as any hidden character might be interfering with the transformation step.

Below is one way to troubleshoot this issue in n8n:

Why It Might Happen

Although your string conversion using .toTitleCase works in most cases, the input “IN PERSON” appears to go through a process where:

1. The node receives “IN PERSON” in all caps (from Gcal).
2. The transformation function is processing the string, but the first word isn’t being fully converted. In your case, it ends up as “in Person” (with just the “P” already correct).

This behavior may occur if the function assumes the string is already partially processed (or if extra casing methods are applied before or after). In many situations, if the input isn’t first normalized (for example, by converting it to lowercase) then applying title-casing, you might end up with an unexpected result.

Suggested Fix

A common workaround is to chain the transformation with a conversion to lower case first. For example, instead of just using:

  {{ $json.section.toTitleCase() }}

try combining the methods like this:

JSCopied
{{ $json.section.toLowerCase().split(' ').map(word => word.charAt(0).toUpperCase() + word.slice(1)).join(' ') }}

This does the following:

1. Converts the entire string to lowercase.
2. Splits the string on spaces.
3. Maps over each word converting its first character to uppercase.
4. Joins the words back together with a space.

This should reliably turn “IN PERSON” into “In Person” regardless of the input casing.

Additional Checks

• Double-check your expression: Ensure that only one transformation is being applied to the input. Other hidden casing functions or an extra transformation could interfere with your expected output.
• Refresh credentials/settings if needed: In rare cases, if you’re caching old values or settings in your workflow, stopping the process (and restarting n8n if necessary) might help apply the new expression correctly.

Using the above workaround should resolve the issue. If you continue to face issues despite this, consider verifying that the transformation function is not being overridden by any global or node-specific settings in your workflow.