Why Does the Connect Frontend SDK Display "Pipedream" Instead of My Custom OAuth Client App Name?

Help
1

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

Hey
I’m using the Connect frontend SDK (@pipedream/sdk v1.8.0) with a custom OAuth client, but users still see “Pipedream” instead of my custom OAuth.
Setup:
• Created custom OAuth client in Account Settings → OAuth Clients (for Google)
• Passing oauthAppId to both createFrontendClient() and client.connectAccount()
• OAuth client is Active with my Google credentials configured
• Project ID, Environment: development
Issue:
Users see “Sign in to continue to Pipedream” instead of my app name. The oauthAppId parameter seems to be ignored.
Verified:
:white_check_mark: OAuth App ID is correct
:white_check_mark: Browser console shows oauthAppId being passed
:white_check_mark: OAuth client configured with Google Client ID/Secret
:white_check_mark: Consent screen has my app name
Question:
Does the frontend SDK support custom OAuth clients? Any additional config needed to make it work?
Thanks!

2

Hi everyone, I’m using Development Mode and testing the Gmail → New Email Received trigger. I’m noticing that new emails can take more than ~15 minutes to arrive.
Questions:

  1. Is there a way to reduce this delay and get closer to real-time delivery?
  2. I didn’t see an option to change the polling interval — is there a setting I’m missing?
    trying with custom auth, but stuck with the OauthAppid. Appreciate any help.
3

Hi > Hi everyone, I’m using Development Mode and testing the Gmail → New Email Received trigger. I’m noticing that new emails can take more than ~15 minutes to arrive.
Could you share how are you creating the Gmail source? Is it on Pipedream UI or via Connect API?

4

Am creating gmail source using connect API.

5

Thanks , could you share the code you used to create the source if possible?

6

Hi Leo, following this -

but my custom oauth screen is not coming up in UI. I am assuming if i pass Oauthappid in connect then it will automatically go to custom Oauth App, not on pipedream default screen.

7

I’m following the document here, paste below:

  1. Follow the steps here to create an OAuth client in Pipedream.
  2. When connecting an account either via the frontend SDK, make sure to include the oauthAppId in pd.connectAccount().
  3. If using Connect Link, make sure to include the oauthAppId in the URL.
    I think it is pretty much answer all of your question
8

Could you take a look and let me know if it’s working?

9

Thanks , it is working. Only issue is that while i deploy the trigger, now i am getting below error if i select webhook.
{
“error”: “observation error”,
“err”: null,
“observations”: [
{
“k”: “hook”,
“ts”: 1762869979203,
“h”: “activate”
},
{
“k”: “error”,
“ts”: 1762869979205,
“err”: {
“name”: “TypeError”,
“message”: “Cannot read properties of undefined (reading ‘endpoint’)”,
“stack”: “TypeError: Cannot read properties of undefined (reading ‘endpoint’)\n at Object.activate (file:///tmp/pdg/dist/code/79416b0c7a464146c564fe80ab335ae4be8986266b422fd087287c4d42311129/code/sources/new-email-received/new-email-received.mjs:379:38)\n at /var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:78:52\n at captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:11)\n at deployedComponentMain (/var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:44:26)\n at file:///var/task/component_maker.mjs:203:17”
}
}
]
}

10

Hi , thank you for your information.

You can check out the Pipedream Connect Demo here to understand how to call creating trigger correctly: One SDK, thousands of API integrations