Publishing Trigger, Invalid Data 400 Headers error

  • 14 January 2021
  • 2 replies


  • App data to Zapier as a Polling Trigger
  • Using one data field to get it done right first - First_Name
  • Images of all of the pieces are below


The app returned "Invalid data for key First_Name: Brian cannot be parsed as a JSON". What happened (You are seeing this because you are an admin): Stack trace: ResponseError: {"status":400,"headers":{"content-type":"application/json"},"content":"{\"statusCode\":400,\"body\":{\"status\":\"INVALID_DATA\",\"message\":\"Invalid data for key First_Name: Brian cannot be parsed as a JSON\"}}","request":{"url":""}} at Object.throwForStatus (/var/task/node_modules/zapier-platform-core/src/http-middlewares/after/throw-for-status.js:7:11) From previous event: at executeHttpRequest (/var/task/node_modules/zapier-platform-core/src/execute.js:22:6) at execute (/var/task/node_modules/zapier-platform-core/src/execute.js:90:12) at input (/var/task/node_modules/zapier-platform-core/src/create-command-handler.js:29:14) at Object.beforeMiddleware.then.newInput (/var/task/node_modules/zapier-platform-core/src/middleware.js:90:22) at bound (domain.js:402:14) at Object.runBound (domain.js:415:12) From previous event: at input (/var/task/node_modules/zapier-platform-core/src/middleware.js:89:45) at loadApp.then.appRaw (/var/task/node_modules/zapier-platform-core/src/tools/create-lambda-handler.js:215:18) at bound (domain.js:402:14) at runBound (domain.js:415:12) at runCallback (timers.js:705:18) at tryOnImmediate (timers.js:676:5) at processImmediate (timers.js:658:5) at process.topLevelDomainCallback (domain.js:126:23) From previous event: at (/var/task/node_modules/zapier-platform-core/src/tools/create-lambda-handler.js:200:10) at (domain.js:349:14) at Runtime.handler (/var/task/node_modules/zapier-platform-core/src/tools/create-lambda-handler.js:192:19) at Runtime.handleOnce (/var/runtime/Runtime.js:66:25)



  • Authentication on OAuth2.0 has been setup successfully
  • Actions completed successfully




This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

Userlevel 7
Badge +10

Paging @ikbelkirasan for help.

Userlevel 7
Badge +9

It looks like that’s a message getting returned from the API endpoint, implying that it’s trying to parse the string value of a query param as a JSON object?  

What I would probably do next here is use Postman or something similar and make the same request from there.  This helps establish if the issue is related to the Zapier integration configuration or if the issue is with understanding what the server is expecting to get passed.  If it works in Postman, we can then try and figure out what’s different about the request being formed by Zapier.  If it doesn’t work in Postman, then we need to troubleshoot the API itself - and Postman is a tool specializing and focusing on just that.