Why Am I Receiving an "Invalid_Type" Error When Creating Google Calendar Events Using Pipedream Payload?

Help
1

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

Hi there, I am having issues with google calendar events, here is the object I am sending in the payload:
{
“id”: “google_calendar-create-event”,
“configuredProps”: {
“googleCalendar”: {
“authProvisionId”: "apn_"
},
“addType”: “detailed”,
“text”: “My event description”,
“calendarId”: “primary”,
“eventEndDate”: “2026-01-16T17:00:00+01:00”,
“eventStartDate”: “2026-01-16T16:00:00+01:00”
},
“externalUserId”: 'f708****************',
“dynamicPropsId”: “dyp_*****”
}
}

And the error I get is:

Error parsing arguments: [
{
“expected”: “‘detailed’ | ‘quick’”,
“received”: “undefined”,
“code”: “invalid_type”,
“path”: [
“addType”
],
“message”: “Required”
}

I have tried sending this field in different formats, for example as I saw in the pipedream demo of the event:

    addType: {
      __lv: {
        label: "Add Detailed Event",
        value: "detailed"
      }
    }

But I always end up with the same error, any idea what can be the problem in these case?

2

Your payload seems right. I assume your dynamicPropsId matches a reloadProps API call passing the “detailed” option for the addType prop.

In any case we’re looking into simplifying this component

3

Try again with the latest version of the component - we’ve just shipped an update that removes the need to reload props if you’re not using recurrence.

4

Thank u, is there any way I can make it work in v1? We would prefer not to migrate to v2 in this moment

5

I would be really thankfull if you can see this case :pray:

6

Do you mean updating the component version? It did not remove support for any of the params you used, it just removed the ‘quick event’ option. So you may not need to use dynamicPropsId at all.

7

I understand, but all my integration with Pipedream is with the v1 of the API, through more than one project. That’s why I’m asking you if there’s a way to make this case of use work in v1 so I don’t have to migrate all the integration through different projects

8

Hi again, I read the documentation and the V2 is only available for the SDK integration, not for API integration. I have multiple proyects connected to Pipedream and all of them via API. Migrating to SDK is a huge load of work to do, and base on your feedback Guillerme this should work using V1 API. What can I do? Can anyone help me here please @U02A06JPKEH @UMZ236G4U @UMZ235TK6 @US8SW2C8G @U09PU2K1G7J @U09N7G9Q62J @URV1X5N2H

9

I think we’re talking about different things here. I recommended you to run the latest version of the component - this is not an update to the API nor the SDK, just the single google_calendar-create-event component that you’re running.

When you retrieve its props, you’ll notice they’ve been slightly changed in our latest update to the component. And the issue you were running into should no longer happen. Let me know if that’s not the case.

10

So exactly the same body should work now?

11

Try removing the addType prop and the dynamicPropsId. But you should have a flow set up to retrieve the component’s available props, then set up the request body accordingly.

12

I think the text prop should be named summary too.

13

But if I don’t send the addType property, it will create a quick or a detailed event? I need specifically detailed events

14

The update we made was so that the action always created detailed events. (we have a quick-add-event component in the google calendar app for quick events)

15

As I mentioned above, you should have a flow that retrieves the component’s props so you know exactly which you need to send: this documentation helps

16

Thank u very much Guilherme. The tool is working perfectly now!