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.

Best answer

Clio Integration: 401 on "API Request (Beta) in Clio" for any Clio Manage api request - Bug?

  • August 27, 2024
  • 1 reply
  • 34 views
J

This is still an issue.

Any updates on if this will get fixed?

Best answer by SamB

Hi @jpcrook, thanks for reaching out here! 🙂

Ah, that other post had been automatically closed due to inactivity. I’ve re-opened it so any further discussions regarding the bug can be had there and will be closing this one now. 

You’ve been added to the bug report so you’ll get an email notification as soon as it’s sorted. There aren’t any updates I can share at the moment however, I’ve just posted another potential workaround in the main thread there which you may want to give a try.

I’ll share a copy of that workaround here in case it’s helpful:

The workaround would be to try using the Custom Actions feature for Clio instead of an API Request action:
22402f5551da0abeb320706e87684122.png

As custom actions handle the requests differently this may help to get avoid those “unauthorizedError” errors. And they have an AI powdered Copilot that will help to get everything set up for you! You can learn more able custom actions here: Create a custom action


Hopefully that will help to get your Zaps up an running in the meantime. 🙂

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
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • Answer
  • August 29, 2024

Hi @jpcrook, thanks for reaching out here! 🙂

Ah, that other post had been automatically closed due to inactivity. I’ve re-opened it so any further discussions regarding the bug can be had there and will be closing this one now. 

You’ve been added to the bug report so you’ll get an email notification as soon as it’s sorted. There aren’t any updates I can share at the moment however, I’ve just posted another potential workaround in the main thread there which you may want to give a try.

I’ll share a copy of that workaround here in case it’s helpful:

The workaround would be to try using the Custom Actions feature for Clio instead of an API Request action:
22402f5551da0abeb320706e87684122.png

As custom actions handle the requests differently this may help to get avoid those “unauthorizedError” errors. And they have an AI powdered Copilot that will help to get everything set up for you! You can learn more able custom actions here: Create a custom action


Hopefully that will help to get your Zaps up an running in the meantime. 🙂

Terms & ConditionsAccessibility statement