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

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