On last March we used Pipedream to integrate Calendly with Google sheets. We were able to transfer the necessary variables from any created or cancelled event in Calendly to a new row in Google sheets.
Now we purchased Calendly to move these integrations into production. However, today the list of variables available for transfer is much shorter and some of the missing ones are critical for our business. According to Github the Calendly APIs have not changed since November 2022, so I wonder if any change has occurred from this side. Thanks in advance for your support.
Danny, if I understand your question correctly, the even shape that I see now is very similar (although not equal) to the one depicted in the link you sent in the previous mail. And the variables depicted in the link do not include the missing ones.
It seems that the Calendly app (as compared to Calendly OAuth app) is the one that we should be using to obtain the full stack of Calendly variables. Is it possible to still use this app, or is there a workaround to reach this full stack through Pipedream?
The event shape that is returned from the Calendly trigger matches what their docs reference for me when I test it, so my assumption is that Calendly might have modified their API or webhook payload at some point.
It looks like some of those fields you’re looking for are available from the existing webhook:
event.creator_name → event.name
event.event.canceler_name → event.payload.cancellation.canceled_by
And the others can probably be retrieved via the Get Event action:
event.location → resource.location
event.start_time_pretty → resource.start_time (you may have to format this timestamp)
I have 2 questions regarding this issue. The first one, why is it that up off to date your competition (Zapier, Make) is able to extract from Calendly all the information I’m looking for, as Pipedream was until recently?
Second, and more important. Since the information is available in Calendly, what can I do to get it?
I’m not a trained developer, and I really like Pipedream, so changing the integration app is not an option. I would really appreciate your guidance in this topic. Thanks a lot.
Hi @starterpapudo , if you have a look at the Calendly API documentation, they are phasing out their API v1 in about two months, and deprecating some of the functionality that was available in the first version of their API. Given that we have migrated to the API v2 already, we are no longer able to support the functionality of API v1 that will soon be deprecated.
Note: API v2 is not backwards compatible with API v1 so the data structure for API v2 responses does not match the API v1 payload. Please refer to the API v2 documentation to see more details about each endpoint.
That being said, you should be able to find the fields you are looking for as Danny mentioned via the Get Event action that we have available.
I am requesting support through this means because I have gotten no response requesting it through your web page.
My workflow integrates Calendly with Google sheets. Data from every new invitee event created with Calendly should get registered as a new row in a Google spreadsheet.
However, if I create 10 new invitees in a row with Calendly, only 3 or 4 of them will get registered in the Google sheet. But all 10 show up in the workflow log as successful events. I don’t think this is normal behavior, and I would really appreciate your help on this.
Hi @starterpapudo, can you please share access to the workflow, as well as a link so that I can have a look at the workflow to debug further? You should be able to find this in your Workflow settings under Support – > "Allow Pipedream Support to access or edit this workflow
Hi @starterpapudo, in the workflow that you shared, the source (Calendly_Solicita) does not appear to be running.
I believe that you may be using an older version of a source trigger as well, can you try to re-configure the source and attach it to the workflow and try again?
Hi Starterpapudo, can you try to remove the trigger, and reconnect it? In addition, can you confirm that the source is running?
Once you do that, if you can run through the example of creating/cancelling events, I’d like to see if this issue is still occurring. Currently, I can’t see any events in the TEST workflow.
