About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Trouble setting up authentication oAuth - "Error parsing response" error

  • 9 March 2021
  • 1 reply
  • 129 views
J
Userlevel 1

Hi Team,

Please refer below error I was getting while trying to signin into my integration in zapier. Please help.

 

Oh, foo.

Zapier could not connect to your account.

Error parsing response. We got: "<!DOCTYPE html> <!-- Build: 1.0.1964.0 --> <!-- StateVersion: 2.1.1 --> <!-- DeploymentMode: Prod" What happened (You are seeing this because you are an admin): Starting GET request to https://possibleworksb2c.b2clogin.com/possibleworksb2c.onmicrosoft.com/oauth2/v2.0/authorize Received 200 code from https://possibleworksb2c.b2clogin.com/possibleworksb2c.onmicrosoft.com/oauth2/v2.0/authorize?p=B2C_1_sign_in_only&client_id=1b1eaf9f-0ae4-417c-9f15-e72149cac4ce&nonce=defaultNonce&redirect_uri=https%3A%2F%2Fzapier.com%2Fdashboard%2Fauth%2Foauth%2Freturn%2FApp127756CLIAPI%2F&scope=offline_access%20openid%20https%3A%2F%2Fpossibleworksb2c.onmicrosoft.com%2F82d73e90-f48a-43f8-a4a7-f4065f149276%2FFiles.Read&response_type=code%20id_token%20token&prompt=login&response_mode=query after 2697ms Received content "<!DOCTYPE html> <!-- Build: 1.0.1964.0 --> <!-- StateVersion: 2.1.1 --> <!-- DeploymentMode: Prod" Error parsing response. We got: "<!DOCTYPE html> <!-- Build: 1.0.1964.0 --> <!-- StateVersion: 2.1.1 --> <!-- DeploymentMode: Prod" Console logs: Stack trace: SyntaxError: Error parsing response. We got: "<!DOCTYPE html> <!-- Build: 1.0.1964.0 --> <!-- StateVersion: 2.1.1 --> <!-- DeploymentMode: Prod" at Object.input.z.request.then.then.resp (/var/task/node_modules/zapier-platform-core/src/execute.js:27:31) at bound (domain.js:402:14) at Object.runBound (domain.js:415:12) at Object.tryCatcher (/var/task/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/var/task/node_modules/bluebird/js/release/promise.js:517:31) at Promise._settlePromise (/var/task/node_modules/bluebird/js/release/promise.js:574:18) at Promise._settlePromise0 (/var/task/node_modules/bluebird/js/release/promise.js:619:10) at Promise._settlePromises (/var/task/node_modules/bluebird/js/release/promise.js:699:18) at _drainQueueStep (/var/task/node_modules/bluebird/js/release/async.js:138:12) at _drainQueue (/var/task/node_modules/bluebird/js/release/async.js:131:9) at Async._drainQueues (/var/task/node_modules/bluebird/js/release/async.js:147:5) at Immediate.Async.drainQueues [as _onImmediate] (/var/task/node_modules/bluebird/js/release/async.js:17:14) 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)

icon

Best answer by SamB 17 August 2021, 16:08

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

1 reply

SamB
Rank
Userlevel 7
Badge +11

Just wanted to follow up here to note that we’ll usually see an “Error Parsing Response” error for the following reasons:

  • API returns non-standard and especially non-JSON output
  • Test API endpoint URL is incorrect

You can find out more about this type of error and how to troubleshoot it here: Documentation - Error Parsing Response

If you try the suggestions on that guide and are still having trouble, please reach out to our Support Team for assistance. The best way to contact them is by using the Get Help form.

Terms & Conditions