Documenting bugs as I find them with the migration process. Sent a bunch to support via email. But posting this one here in case anyone else is using Zapier.
Studio Products are gone in Zapier as an option. Maybe needs to be updated to “Access Levels” to align with new system? Not sure!
Our business relies on this as we take sales on a 3rd party site then use Zapier to trigger the user creation & access granting in Pickaxe for fulfillment.
Thanks!
Thanks for the detailed heads-up, Stephen. I logged this internally as PRD-506 so the team can restore the Studio Products/Access Level hook in the Zapier connector ASAP. I will circle back here as soon as the updated Zapier build is live.
@stephenbdiaz thanks for reaching out! I checked with our engineers, and any set ups you previously had using Studio Products should still be functioning just fine (please let us know if this isn’t the case!). Meanwhile, we are adding an Access Groups endpoint, which should be up and running very soon - if you like, I can let you know when it’s been successfully added!
Hi @stephenbdiaz ,
Thank you for your patience.
We have now updated the Zapier integration and added the Access Group endpoint to align with the new system.
Woo woo thank you! Appreciate you guys!
@lindsay_support @danny_support hey update on this, we’re seeing Zapier error out a bunch the last couple of weeks. Not sure if there was a change? We’re using the Create User feature but not sure if that’s why it’s glitching out?
The error says it’s an issue with the Studio API Key or expired OAuth access token, see secreenshots.
Hi @stephenbdiaz ,
Thank you for reaching out, and thank you for your patience.
There was a bug related to Zapier authentication tokens expiring, which is likely why you were seeing OAuth access token errors. Our engineers have already pushed a fix for this.
Please reconnect your Pickaxe account to Zapier and try again. I tested the Create User action, and it worked as expected on my side.
Also, I flagged the incorrect Create User description to our engineers. Even though the description mentions documents, that appears to just be a typo. The Create User action itself should still work as expected.
Please let us know if you run into any issues after reconnecting.
