If your n8n workflow works one day but is broken the next... And...
Tom@tomcrawshaw01
5 views
Jun 28, 2025
~2 min read
1
If your n8n workflow works one day but is broken the next...
And you have no idea what changed.
Here's how to troubleshoot any automation issue: 🧵👇
And you have no idea what changed.
Here's how to troubleshoot any automation issue: 🧵👇
2
When your HTTP request node throws an error, don't stress.
I use the "Claude Debug Method":
- Grab the API documentation
- Copy the error message
- Screenshot your node settings
- Screenshot the previous node's output
- Feed it all to Claude
Works 95% of the time.
I use the "Claude Debug Method":
- Grab the API documentation
- Copy the error message
- Screenshot your node settings
- Screenshot the previous node's output
- Feed it all to Claude
Works 95% of the time.
3
Step 1: Get the API docs
Most people skip this and wonder why their requests fail.
The API documentation tells you:
Exact endpoint URLs
Required headers
Authentication format
Body structure
Query parameters
Without it, you're just guessing.
Most people skip this and wonder why their requests fail.
The API documentation tells you:
Exact endpoint URLs
Required headers
Authentication format
Body structure
Query parameters
Without it, you're just guessing.
4
Step 2: Screenshot everything
When I hit an error, I capture:
The exact error message from n8n
My current node configuration
The output data from the previous successful node
This gives Claude the full context it needs to spot the issue immediately.
When I hit an error, I capture:
The exact error message from n8n
My current node configuration
The output data from the previous successful node
This gives Claude the full context it needs to spot the issue immediately.
5
95% of HTTP request errors happen in these 5 places:
- Headers (wrong format/missing auth)
- URL structure (incorrect endpoint)
- Body parameters (wrong JSON structure)
- Query parameters (missing or incorrect)
- Credentials (expired/misconfigured)
Check these first.
- Headers (wrong format/missing auth)
- URL structure (incorrect endpoint)
- Body parameters (wrong JSON structure)
- Query parameters (missing or incorrect)
- Credentials (expired/misconfigured)
Check these first.
6
What trips up 99% of builders:
- Capitalization matters. "Content-Type" ≠ "content-type"
- One wrong letter = total failure
- JSON variables must show GREEN text (red = broken)
- Variable paths must match previous outputs exactly
The devil is in these details.
- Capitalization matters. "Content-Type" ≠ "content-type"
- One wrong letter = total failure
- JSON variables must show GREEN text (red = broken)
- Variable paths must match previous outputs exactly
The devil is in these details.
7
I paste this into Claude:
"Here's the API documentation: [paste docs]
Here's my error: [paste error]
Here's my node setup: [attach screenshot]
Here's the previous node output: [attach screenshot]
What's wrong and how do I fix it?"
Claude spots the issue in seconds.
"Here's the API documentation: [paste docs]
Here's my error: [paste error]
Here's my node setup: [attach screenshot]
Here's the previous node output: [attach screenshot]
What's wrong and how do I fix it?"
Claude spots the issue in seconds.
8
This debugging method has saved me 100+ hours of troubleshooting.
Native integrations work great once APIs are set up correctly, but HTTP requests need this systematic approach.
Want more n8n automation strategies?
Join 700+ readers getting my AI Client Machine newsletter: sms.emailalchemy.co/newsletter
Native integrations work great once APIs are set up correctly, but HTTP requests need this systematic approach.
Want more n8n automation strategies?
Join 700+ readers getting my AI Client Machine newsletter: sms.emailalchemy.co/newsletter