WhatsApp node has stopped receiving images

Hi everyone,
I’d like to check if anyone else is experiencing this issue. Until recently, the WhatsApp node was receiving images without any problems, but now it has stopped working. Text messages are still coming through correctly, but images are no longer received or processed in the flow.
Does anyone know if this is due to a change in the API, a pending update, or a known issue?
Any guidance or solution would be greatly appreciated.
Thanks,

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hi @July_Suarez

Just wanted to share that we have a WhatsApp workflow automation running, and it’s currently processing images without any issues — so it doesn’t appear to be a general or widespread problem.

Could you please check the Executions tab in your n8n instance? Look for any errors or failed executions there, as that might help pinpoint where the issue is occurring — whether it’s in the WhatsApp node itself or further down the flow.

Let us know what you find — happy to help troubleshoot further!

Hello July_Suarez, i’ll try to answer yaa.

I think this is a recent change from Whatsapp’s side. Text still comes through directly, but images/videos dont include the download link anymore, you just get a media ID.

Maybe you can catch the webhook as usual, and then you can use HTTP Request node to call the Graph API, just like this:

GET https://graph.facebook.com/v17.0/<MEDIA_ID>
Header: Authorization: Bearer <your_WA_token>

This gives you the real file URL..

And then you need to add another HTTP Request node to download the file from that URL (again with the same auth header).

Thats it i think i can help you. Hope this will be works for you! :blush::raising_hands:

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.