Why Does Google Calendar Show "Connected" But Connect Component Actions Fail with "auth_required"?

Help
1

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

Looking for advice: Google Calendar “connected” but actions fail with auth_required
TL;DR: Gmail and Zoom work via Connect; Google Calendar shows “Successfully connected” in the popup, but Connect component actions still fail with auth_required (and observations are often empty). Has anyone hit this and found the fix?
Context
• Using Connect components via actions.run (server-side)
• External user flow; token/client caching in app is working (cache-miss → cache-hit confirmed)
• Gmail + Zoom succeed; only GCal fails after “connected”
How we call it

{
  "id": "google_calendar-list-events",
  "external_user_id": "<user_id>",
  "configured_props": {
    "google_calendar": { "authProvisionId": "<apn_xxx>" },
    "calendar_id": "primary",
    "start_datetime": "2025-08-13T08:50:09Z",
    "end_datetime": "2025-08-13T09:20:09Z"
  }
}

(similar for google_calendar-create-event with summary/start_datetime/end_datetime/attendees)
What we’ve tried
• Reconnect GCal multiple times (popup says “Successfully connected”)
• Sync via accounts.list; DB shows multiple GCal accounts; we choose the newest
• Deleted duplicates at source; tried a full relink with a fresh Connect token
• Defensive fresh-lookup of the latest accountId before each call
• Still seeing auth_required; verify endpoint marks GCal as not connected
Questions for the community
• Has anyone seen GCal show “connected” but actions continue to return auth_required?
• Are these the right action IDs for Connect today?
• google_calendar-list-events, google_calendar-create-event
• Is authProvisionId still the correct field under configured_props.google_calendar?
• Any scope gotchas (specific Calendar scopes required beyond typical read/write)?
• Dev-mode caveats: does the user need to be signed in to pipedream.com in the same browser session for the token to be usable?
• Best practice to “force relink” cleanly:
• Do you purge all GCal apn_* accounts at source, then relink once?
• Any sequence that reliably yields a good token?
Happy to share run details privately if helpful. Thanks in advance!

2

Hi
i faced this before
Here is the info

"configured_props": {
    "google_calendar": { // wrong action name
 "authProvisionId": "apn_xxx" },
    "calendar_id": "primary",
    "start_datetime": "2025-08-13T08:50:09Z",
    "end_datetime": "2025-08-13T09:20:09Z"
  }

seem like you passed app name instead of provided by action’s props info

Need to pass correctly
we got
type: “app”
and name as: “googleCalendar”
try

{"configured_props": {
    "googleCalendar": { 
 "authProvisionId": "apn_xxx" ...},

Screenshot from 2025-08-13 14-31-35.png
Screenshot from 2025-08-13 14-31-35.png969×457 86.2 KB

3

you good sir, solved my problem as well, thank you. I was missing the APN for the request. Thanks!

4

My pleasure :handshake:

5

it’s weird it’s not in the docs and does not raise a descriptive error

6

Right…
Agree that doc’s is not clear enough, even though at some places it is show depricated stuff

You can look on the contribution page to know about the params and test on demo project if you faced any api related issue

7

This is amazing! Thanks team let me try this!!