Why does Google Calendar's New Upcoming Event Alert Component Require Pipedream API Key even when already connected to PD?

Bugs
1

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

Google Calendar > New Upcoming Event Alert Component requires Pipedream API key. This looks like a bug as I am already connected to PD as I am using Connect and all other actions work without API key as Configurable Params

2

Hi , actually it is expected to have you input your Pipedream API Key.

The source needs Pipedream API Key to renew Google Calendar webhook subscription

3

I’m confused because other triggers don’t require it. This is a customer-facing UI and users don’t have access to the Pipedream API. They connect their Google Calendar account and expect it to work. Am I missing something?

4

Hey , thank you for your input. I’ll check with the team on how to handle this case.

Just to confirm, you’re using Pipedream connect right?

5

Yes. Thank you!

6

cc , could you share your input here once you have a chance?

My take is that we can treat the Pipedream API Key as the “special props” where it will automatically uses Connect SDK’s Pipedream API Key and hide for end-user

7

That trigger is a bit of a special snowflake and it doesn’t currently work in Connect, we’re discussing how to handle in that context

8

Posted thread to Discourse: Why Does Google Calendar's New Upcoming Event Alert Require a Pipedream API Key Despite Already Being Connected?

9

We’re using Pipedream Connect for our app and have a similar use case.

Currently we’re using these Pipedream APIs:

  • Connect API for OAuth account management (Google Calendar and Gmail)
  • Proxy API to fetch calendar events and Gmail messages on-demand

We poll for new calendar events periodically, but would love to set up webhooks to get real-time notifications when calendar events are added, deleted, or updated. Is this possible through Connect?

Also - quick question on the OAuth flow: Can we get OAuth tokens directly from Pipedream’s Connect API after users authenticate? Or do we need to send users through a separate Google OAuth onboarding to get tokens ourselves? Right now we’re relying entirely on Pipedream’s proxy endpoints which works great, just curious about if I’m able to get our users’ OAuth tokens for Gmail/Calendar in case I want to hit google ApIs that are not supported by pipedream proxy

10

We poll for new calendar events periodically, but would love to set up webhooks to get real-time notifications when calendar events are added, deleted, or updated. Is this possible through Connect?
Yes, check out how you can deploy triggers: Deploying Triggers - Pipedream

11

Also - quick question on the OAuth flow: Can we get OAuth tokens directly from Pipedream’s Connect API after users authenticate?
If you’re using your own OAuth clients for any of those apps, yes. If you’re relying on Pipedream’s OAuth for Google Calendar for example, then no, we don’t currently expose the raw access tokens to developers. Some more info is here: OAuth Clients - Pipedream