N8n Webhook suddenly stopped receiving requests from Z-API – anyone else facing this?

Questions
1

Hey everyone!

I’m facing a strange issue and wondering if anyone has experienced something similar or has ideas on what might be going on.

:brain: Context

  • I’m using n8n (self-hosted), version 1.103.2
  • I have a production workflow for a sales agent, triggered by a webhook
  • This webhook receives requests from Z-API (a WhatsApp integration)

Everything had been working flawlessly for a long time – until suddenly, the webhook stopped triggering. No changes were made to the flow or infrastructure.

:magnifying_glass_tilted_left: What I’ve tried so far

  • Restarted the n8n instance
  • Reconnected Z-API to ensure integration is active
  • Manually sent a POST request to the webhook using a Python script (requests.post)

:green_circle: Result: When triggered manually via Python, the webhook works as expected and the flow executes correctly.

:red_circle: Issue: Requests from Z-API no longer reach the webhook – they just vanish as if blocked or silently ignored.

:red_question_mark: Anyone else going through this?

  • Could there have been a recent change or update on the Z-API side?
  • Are there any known security measures, CORS rules, IP blocking, or headers in n8n I should check?
  • Any tips on how to debug webhook calls that don’t show up in n8n?

:package: Environment

  • n8n version: 1.103.2
  • Hosting: Self-hosted
  • Trigger: Webhook node
  • External integration: Z-API (WhatsApp)
  • Manual testing: Works fine via Python script (requests.post)

Any insights or shared experiences would be super appreciated :folded_hands:
If others are experiencing this too, we might be able to identify a broader issue together.

2

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