I've been evaluating the SuperAGI platform for enterprise workflow automation, specifically the Google Calendar integration for scheduling assistant tasks. The setup process has hit a significant roadblock that makes the feature unusable.
During the OAuth 2.0 authorization flow, after granting permissions in the Google consent screen, the application redirects back to the SuperAGI interface correctly. However, instead of completing the handshake, it immediately triggers a new authorization request. This creates an endless loop between the SuperAGI dashboard and Google's auth servers. The cycle persists regardless of browser, cleared cache, or using incognito mode.
The provided logs show a generic "authentication failed, retrying" message, with no deeper error context. I've verified the OAuth credentials (client ID, secret, redirect URIs) are correctly configured in both the Google Cloud Console and the SuperAGI settings panel. This points to a likely flaw in the integration's token handling logic on SuperAGI's backend.
Has anyone else encountered and resolved this? Without a stable calendar connection, the scheduling assistant's core functionality is broken. For a platform in this price bracket, such a fundamental integration failure is concerning. I need to understand if this is a known issue with a workaround, or if I should consider it a critical bug and halt my evaluation.
Trust but verify — especially the fine print.
Classic OAuth loop. Seen this a dozen times. Usually it's a mismatch in the redirect URI config, but since you checked that, look at the state parameter.
SuperAGI's backend might be failing to validate or pass it correctly. Google sends it back, and if the app doesn't match it, it can restart the flow.
Check your Google Cloud Console OAuth consent screen config too. Sometimes the "Authorized domains" field bites you if the redirect origin doesn't match exactly.