I’m the developer currently maintaining our Wolfram Service Connections. I apologize for what you’re experiencing atm. Google has updated its privacy policy and when I was refactoring our google related connections it triggered a new verification process for our underlying “web apps”. I plan on addressing this issue in the short term.
If you have a registered and approved app in the Google Cloud Console, it is certainly possible to use your own Client ID and Client Secret with SercuredAuthenticationKey. However, I suggest you use URLRead with your already acquired token for the time being.
If you have a valid app registered in the google cloud console, and a set of credentials, you can try this after making sure that “https://www.wolframcloud.com/objects/forms/oauth/verifier20/” is added to the list of valid redirect uris in your app:
Unfortunately, support for refreshing access tokens (like google’s case which expires after an hour) is yet to be properly handled. So, you will have to refresh your service connection each time your token expires. The plan to improve and optimize this is on the roadmap but will not be available as soon as I would like to promise you.
If there’s any other inquiry, feel free to email me at juanl@wolfram.com,
I was going to create an Alexa skill today to integrate with ChatGPT for answering questions like “what’s on our calendar this Friday?” but was blocked by this issue as well.
Any update on solving this issue? I got this message when logging in after calling:
ServiceConnect["GoogleCalendar", "New"]
Access blocked: wolfram.com has not completed the Google verification
process *********@gmail.comwolfram.com has not completed the Google
verification process. The app is currently being tested, and can only
be accessed by developer-approved testers. If you think you should
have access, contact the developer. If you are a developer of wolfram.com, see error details. Error 403: access_denied