Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

  • Home
  • Get Help
  • Troubleshooting
  • Halo Service Solutions error: invalid_requesterror_description:The specified Client ID has been denied access.

Hi, 

I’m trying to use the Halo Service Solutions ZAP.  When attempting to sign in, Zapier asks for some information 

 

Which I cut and paste from The Halo Zapier integration screen from within Halo. 

 

However, when I click “Continue” -I am greeted with an error:

“

error:invalid_requesterror_description:The specified Client ID has been denied access. This means that either the client_id parameter is incorrect or that the url you have entered is incorrect.”

 

Looking at the logs, I can see that Zapier is sending over a client_id that Halo is not aware of.  

 

How can I edit the client_id in Zapier to one that Halo generates for the integration???

Hi @MikeR900 

Good question.

There are no help articles available for this Zap app, so it may be best to try opening a ticket with Zapier Support: https://zapier.com/app/get-help

FYI: Most apps on Zapier are built and maintained by the app developers themselves, so if there’s a bug with the integration it may be up to Halo to fix.

I solved my own problem. 

The Halo ZAP uses a hard-coded client_id.   Halo has a Zapier Integration that must be enabled. It is not obvious on the Halo side if it is enabled or not.  After confirming it was enabled, the connection succeeded. Better documentation on the ZAP side would have helped.

 

Hey, thanks for coming back to share your feedback and success with the community, @MikeR900!

Glad to hear this is up and running now. 🙂

Terms & Conditions