Is n8n’s HTTP Request Node Blocking POST Requests with Null Numeric Fields?

Hi n8n’ers,

I suspect there’s a bug in the HTTP Request Node when performing an HTTP POST to the Bubble data API endpoint. The request fails whenever a numeric field contains a null value.

The odd part is that if I copy and paste a single record from the generated output (the JSON shown in the node’s right panel) into Postman, the POST works perfectly.

I also tried sending the HTTP Request to Webhook.site (similar to Pipedream’s RequestBin) – the endpoint accepts anything regardless of JSON syntax errors. It successfully receives the request when the numeric field has a valid number, but fails when the field is null. This suggests that n8n might be rejecting the request before it’s even sent.

Another clue is that even when I change the credentials on the send, n8n returns the same error, indicating that the issue occurs before any response is received from the endpoint.

I’ve read that n8n has had difficulties handling null values in the past and that some cases still cause issues. Is this a known problem? If so, are there efficient workarounds to handle null values in numeric fields?

Thanks in advance for your help.

---

n8n Setup Information:

• n8nVersion: 1.74.3

• Platform: npm

• NodeJsVersion: 20.18.1

• Database: sqlite

• ExecutionMode: regular

• Concurrency: 5

• License: community

• ConsumerId: 00000000-0000-0000-0000-000000000000

• In storage:

  • Success: all
  • Error: all
  • Progress: false
  • Manual: true
  • BinaryMode: filesystem

• Pruning:

  • Enabled: true
  • MaxAge: 168 hours
  • MaxCount: 2500 executions

• Client:

  • UserAgent: mozilla/5.0 (windows nt 10.0; win64; x64; rv:134.0) gecko/20100101 firefox/134.0
  • IsTouchDevice: false

Generated at: 2025-01-21T15:20:11.500Z

Images: