I’m working on setting up webhook connections between my WordPress installation and Zapier using Cloud9 IDE for testing purposes. The plan is to get everything working here before I deploy to a real hosting environment.
My WordPress site runs perfectly fine within the Cloud9 environment, but I keep running into problems when attempting to link my Zapier account with the WordPress instance. Every time I try to establish the connection, I get this error message:
“We hit an error adding your new account authorization failed: ResponseError()”
I suspect this might be related to CORS configuration issues, but I’m not sure how to troubleshoot the authentication process from Zapier’s side.
Has anyone here managed to get Zapier working with a WordPress site running on Cloud9? Did you need to configure any special CORS headers or settings to make the integration work properly?
had this same problem last month! It’s not a cors issue - zapier needs a stable endpoint for handshakes. cloud9 workspaces sleep and urls change, which breaks zapier’s auth flow. use ngrok to tunnel your cloud9 instance. just run ngrok pointing to your workspace port and use that url in zapier instead. worked perfectly for me.
The ResponseError() you’re encountering stems from Cloud9’s security measures rather than any issues with your CORS configuration. During my testing with WordPress integrations, I found that Cloud9 restricts external access, which complicates the two-way communication necessary for Zapier’s authentication. Specifically, the OAuth process breaks when Zapier attempts to verify your site’s credentials. To avoid these complications, consider setting up a local development environment using Docker or XAMPP for your Zapier testing. This way, you’ll have full network control and can bypass the limitations imposed by Cloud9. Once you have everything functioning locally, transitioning to a live environment will be relatively straightforward, as traditional hosting does not impose these constraints.
I hit the same issue testing Zapier integrations on Cloud9. The problem is Cloud9’s dynamic URLs - Zapier can’t reliably reach them for webhook verification. When Zapier tries to connect, it sends a verification request back to your WordPress site, but Cloud9’s networking usually blocks these external requests. I got around this by exposing the workspace through a public URL using Cloud9’s preview feature. You’ll also need to make sure your WordPress REST API endpoints are enabled. First, check if you can access your-cloud9-url/wp-json/wp/v2/ directly. If that works, it’s definitely a connectivity issue with Zapier reaching your environment, not a CORS problem.