Skip to main content

This is still an issue.

Any updates on if this will get fixed?

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. 🙂