“It
works on my machine.”
That sentence has humbled more developers than any complex bug ever will.
A developer messaged me recently.
You could feel the frustration in his voice.
He was building a WhatsApp automation using n8n and the Meta WhatsApp Cloud API.
Everything looked right.
The nodes were clean.
Credentials were correct.
Logic made sense.
But nothing was happening.
No trigger.
No message.
Just silence.
First Problem: Meta wouldn’t even let him through onboarding.
Most people would start clicking around randomly.
I didn’t.
I looked at the pattern of the restriction.
It wasn’t a technical misconfiguration.
It was a trust issue.
The Facebook Page tied to the setup had activity history that likely triggered Meta’s internal checks.
So I told him:
“Don’t fight it. Start fresh.”
New Business Manager.
Clean setup.
He passed the first gate.
Second Problem: The “Bad Request” Ghost
Now the integration connected… but n8n showed:
“Bad Request”
“No trigger output”
Empty execution logs
This is where panic usually starts.
He asked me:
“How do you even know where to look?”
I didn’t touch his nodes.
I asked one question.
“Are you running this on localhost?”
He said yes.
And that was it.
The Simple Truth
When Meta sends webhook events, it needs a public address.
If your webhook URL says:
That only exists on your laptop.
Meta cannot send data to your personal computer sitting behind your WiFi router.
It needs:
A public IP
HTTPS
A secure handshake
Without that, it doesn’t matter how perfect your workflow is.
The automation isn’t broken.
It’s unreachable.
The Fix
We moved his n8n instance to the cloud.
Configured HTTPS properly.
Seconds later:
Webhook verified.
Trigger fired.
Messages flowing.
You could literally hear the relief.
Nothing was wrong with his logic.
The environment was the real issue.
The Bigger Lesson
Automation isn’t just about connecting nodes.
It’s about understanding how systems talk across the internet.
APIs don’t care that it “works on your machine.”
They care if they can reach you.
That’s the difference between building workflows…
And architecting systems that actually run in the real world.
And honestly?
Solving these invisible problems is my favorite part of what I do.