n8n HTTP request to 17track fails with "invalid data submitted", but works in Postman?

Help me Build my Workflow
1

Hey everyone,

I’m stuck on an n8n workflow and could use some help.

I have an HTTP node that makes a POST request to the 17track API to register a new tracking number. The problem is, 17track keeps responding with an invalid data submitted error.

The strange part is that when I copy the exact same URL, headers, and JSON body into Postman, the request works perfectly and the tracking number is registered without any issues. This makes me think it’s an n8n-specific problem.

What I’ve tried so far:

  • Double-checking my 17token and Content-Type: application/json headers.
  • Manually pasting the JSON body into the node to ensure there are no issues with expressions.
  • Even using a fixed, hardcoded tracking number that I know is valid.

I feel like I’m missing something obvious about how n8n’s HTTP node formats or sends the request. Has anyone run into a similar issue where a request works in Postman but not in n8n?

I’d appreciate any ideas or suggestions! Thanks.
Reference api doc API Docs | 17TRACK

image
image1069×853 45.3 KB

image
image1371×797 54.5 KB

2

You put the wrong field I believe.

Here is the fix one

Change the JSON to your’s.

3

Thanks man , got figured out