I have a custom agent that uses Google Drive actions (Custom OAuth). When I use the agent via the Slack extension, the Jira authorization (Custom OAuth) form loads fine and I can create issues without problems, but the Google Drive action fails because the OAuth consent screen is unable to load inside Slack.
Has anyone managed to make Google Drive work from non-interactive surfaces like Slack? Is there a possibility to configure this integration using Service-to-Service OAuth to avoid the interactive consent entirely?
Hi @Matheus_Resende
Google Drive’s OAuth consent requires a browser popup to complete sign-in. Unfortunately, the Slack extension is unable to render that popup, which is why the authorization fails there. Jira’s auth form works fine because it’s compatible with Slack’s webview constraints.
At this time, the Google Drive action connector does not support Service-to-Service OAuth, only interactive OAuth methods (Default OAuth app or Custom OAuth app) are available.
As a potential workaround, you could try completing the Google Drive authorization from the Amazon Quick web console first, where the popup loads normally. If the stored credentials carry over to the Slack extension for your user, subsequent actions should work without re-prompting for consent. Please test this approach and let us know if it resolves the issue.
For more details, please refer to the following documentation:
Hi @Matheus_Resende,
Hope everything is well with you! Just checking back in since this thread hasn’t received a response in a while. Was the above reply helpful to you or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!