Problem in node ‘WhatsApp Business Cloud‘ No execution data available

Questions
1

Describe the problem/error/question

Trying to setup the simple Whatsapp bot.

What is the error message (if any)?

If i put a parameter in Recipient field, i’m getting "Problem in node ‘WhatsApp Business Cloud‘ No execution data available"error. If it’s a fixed same number - it’s sending the message properly.

Screenshot 2025-03-12 at 19.39.04
Screenshot 2025-03-12 at 19.39.041031×847 77 KB

Please share your workflow

{
“nodes”: [
{
“parameters”: {
“updates”: [
“messages”
]
},
“type”: “n8n-nodes-base.whatsAppTrigger”,
“typeVersion”: 1,
“position”: [
-460,
0
],
“id”: “e5601c1a-41ca-40ea-bea1-a541db9d5a58”,
“name”: “WhatsApp Trigger”,
“webhookId”: “d434c7d1-c5b0-4d3f-be4f-25644001820c”,
“credentials”: {
“whatsAppTriggerApi”: {
“id”: “ypxh9NJxpnxamP8D”,
“name”: “WhatsApp OAuth account”
}
}
},
{
“parameters”: {
“operation”: “send”,
“phoneNumberId”: “578514435350301”,
“recipientPhoneNumber”: “+995555941965”,
“textBody”: “sucess”,
“additionalFields”: {}
},
“type”: “n8n-nodes-base.whatsApp”,
“typeVersion”: 1,
“position”: [
-160,
0
],
“id”: “e8ebc985-f580-4db4-a34b-eef76ca1d438”,
“name”: “WhatsApp Business Cloud”,
“webhookId”: “5caef0f9-9fb3-456b-b948-69532fdd45ac”,
“credentials”: {
“whatsAppApi”: {
“id”: “lgy7KmIjAYWaBDtv”,
“name”: “WhatsApp account 2”
}
}
}
],
“connections”: {
“WhatsApp Trigger”: {
“main”: [
[
{
“node”: “WhatsApp Business Cloud”,
“type”: “main”,
“index”: 0
}
]
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “08f1fb6a3167d703a71bffa514e575d9656e37200509ade0f55075447af38df2”
}
}


## Share the output returned by the last node
<!-- If you need help with data transformations, please also share your expected output. -->

## Information on your n8n setup
- 1.82.1
- **default: SQLite**
- **n8n EXECUTIONS_PROCESS setting (default: own, main):**
- **Running n8n via : Browser**
- **Operating system: MacOS Version 15.3.1 (24D70)**
1 Like
2

I just realized, that same error occurs if i use any expression in parameters - phone number or message text.

3

Having the same error here, It happens if I use any expression in the parameters, both phone number or message text. If Its a fixed number and message, it works

4

@Nikita_Semenov @Angel_Barraza

Try casting the output as a string. Like:

{{ $json.messages[0].from.toString() }} or
{{ String($json.messages[0].from) }}

5

Already tested - nope.

6

Hi, I’ve tried that already, the issue only happens when I use parameters in the recipient phone number or text body fields. However, if I hardcode both values, the message sends successfully.

Things I’ve Tried (Still Getting the Error):

  • Converted values to .toString() → No change.
  • Added a “Set” node before the WhatsApp node to ensure data exists → Still fails.
  • Tried different combinations of fixed/dynamic values:
  • Fixed phone + dynamic text → Error
  • Dynamic phone + fixed text → Error
  • Fixed phone + fixed text → Works
  • Copied and pasted the entire workflow to a new one → Same error.

The only way I can get the WhatsApp message to send is if I “hardcode” both the phone number and text body. If I try to use parameters, the execution fails with “No execution data available.”

Any ideas on what might be causing it or how to fix it?

Thanks in advance!

7

Bizarre.

Are you on latest n8n? @Angel_Barraza @Nikita_Semenov

8

Yes. 1.82.1

10

This is potentially something to submit a bug report over. I cannot confirm locally tho.

11

Yes, Running version [email protected]

12

I have the same problem from version 1.82.0 and 1.82.1
it’s working in 1.81.3

13

I have the same problem, it started happening in version 1.82.0

14

@Angel_Barraza @Nikita_Semenov @Iwan_Budihalim @Alejandro_Quesada

I investigated and someone did in fact create a bug report on github. There are multiple reports. This is in fact a bug. They updated they are looking into the issue.

15

I’m having the same error you mentioned. I’ve tried everything you mentioned and everything else I could think of. When the fields are stable, the message is sent. But if I extract the field from a previous node, I get that error.

16

I’m having the same issue after update

17

I have the same problem since updating today from 1.81.4 to 1.82.2.

This was working fine in 1.81.4 and now all WhatsApp Sends fail.

Rolling back to 1.81.4 fixes it.

18

@Federico_Mansilla @vivianambrose @anthonyjhicks

As I showed above, the bug is validated by the team, and has not yet been fixed.

Updated link to track bug progress:

1 Like
19

do you know how to roll back to other versions in self hosted? really need this to work now for my clients lol

20

If you’re using docker, specify the version in the tag, rather than latest n8nio/n8n:1.81.4

1 Like
21

New version [email protected] got released which includes the GitHub PR 13910.

3 Likes