WhatsApp Issue with the Latest n8n Update

Issue: After updating to the latest version of n8n, the WhatsApp integration is not functioning correctly. The problem affects phone number formatting and message delivery.
:mag: Observed Behavior: 1. Phone Number Formatting Issue: • In previous versions, phone numbers like +31688888188 and +31619971032 were correctly recognized. • After the update, the workflow fails to detect or replace phone numbers correctly in formatted messages. • Possible Cause: The update may have changed how Regex or text processing works inside n8n. 2. Message Delivery Problems: • WhatsApp messages generated inside n8n are not being processed as expected. • Some messages fail to format correctly (e.g., links or rich text not displaying properly). • The WhatsApp node may not be encoding messages correctly before sending. :warning: Impact: • Workflows using WhatsApp messaging no longer function correctly. • Businesses relying on WhatsApp for automated responses or confirmations may experience failures. • Users have to manually correct messages before sending. :mag_right: Possible Causes: • Changes in n8n’s text processing engine. • Updates to the WhatsApp API handling within n8n. • Issues with new dependency versions (e.g., WhatsApp libraries). :hammer_and_wrench: Suggested Fixes: • Rollback n8n to an earlier working version as a temporary fix. • Check changelogs for updates that might have modified text processing. • Verify WhatsApp API changes that could affect message formatting. • Re-test regex conditions in workflows to ensure proper detection. :pushpin: Steps to Reproduce the Issue: 1. Upgrade to the latest n8n version. 2. Run a workflow that formats a WhatsApp message (e.g., inserting phone numbers). 3. Observe that phone numbers are not replaced correctly or messages fail to send properly.

Might be related to

@Cislink_NL can you specify what n8n version you are running, and whether you are self-hosting or using cloud?

The version that I am currently running to get the whatsapp node working for accepting the dynamic params is the version 1.81.4


This case is is indeed the same as mentioned in the topic

@Cislink_NL

consider clicking the ‘solution’ button under my reply :slight_smile: