Does Pipedream Connect Support Direct API Calls and Access to OAuth Tokens for Google APIs?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi everyone! I’m exploring Pipedream Connect for Google Drive integration.

Context:
• Building a feature where users sync their Google Drive folders to our app
• We have a direct Google integration, but hit a roadblock with Google’s CASA Tier 3 certification requirement
• Looking to use Pipedream’s OAuth client as an alternative
Specific Challenge: I need to implement the Google File Picker, which requires OAuth credentials. The Pipedream docs mention:

“To retrieve credentials for a connected account for OAuth apps (Slack, Google, etc), the connected account must be using your own OAuth client.”
Question: Does Pipedream Connect support:

  1. Direct API calls using Pipedream’s OAuth authentication (beyond predefined triggers/actions)?
  2. Accessing OAuth tokens/credentials to use with Google APIs like the File Picker?
    Or is Connect limited to only the predefined triggers and actions?

Thanks in advance for any guidance!

2

Hey Kayden, I also saw your email, but responding here — would the Connect proxy work for your use case? Connect API Proxy - Pipedream

3

Does this mean you need your own Oauth client for each integrated service you want to use? Unless that service supports dynamic Oauth?

4

The Connect proxy does support using Pipedream’s OAuth clients, if that’s what you’re asking?

5

Not sure what you mean by dynamic OAuth?

6

Here’s my understanding, let me know if I’m wrong:

If you want to use the Google Drive Picker in your frontend, you must use your own Google OAuth client for the connection so you can retrieve the access token.

The Pipedream Connect API Proxy is only for backend API calls and does not expose the access token for use in frontend components like the picker unless you use your own OAuth client.

So Connect proxy wouldn’t work in this situation.

7

Got it, that is accurate, yes.

8

Dynamic Oauth https://oauth.net/2/dynamic-client-registration/
Dynamic client registration, a feature of OAuth 2.0, allows clients to register with an authorization server at runtime without manual pre-registration.
We use it over MCP with our Scout Agents. It Takes the pain out of setting up an Auth client within every integration we want our users to connect with. But, not all integrations support this yet. So we are looking at solutions like Pipedream to allow users to connect wherever, without us having to manually create Auth clients in every integration.
https://www.scoutos.com/

9

Apologies, I might be getting off topic of this thread

10

Interesting, what APIs have you used dynamic clients for? I don’t see that mentioned in Scout’s docs?

11

We’ve only found notion mcp supports that dynamic Oauth client registration so far.

12

Got it, yea I’ve never come across it before.

13

But since most services have yet to support it, we’re looking at other solutions to help connect scout users with there products. Y’all have a ton of integrations, so I’ll play around with this later to see if scout can utilize pipe dream to streamline authentication (and maybe tooling) for integrations.

14

To confirm, you’re a Scout customer? So you’re using Scout inside your product? I’m not totally sure I’m following the relationship between your product and Scout.

15

I’m a developer at Scout looking to expand our list of integrations that Scout users can connect to.

16

Ah got it, sorry, your email address confused me. Would it help to hop on a call? I lead product for Connect.

17

Yeh that’d be helpful thanks - available for next couple hours today

18

Will DM you