Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CAL-3505] Issue with Webhooks (Meeting started/ended triggers) #14685

Closed
PeerRich opened this issue Apr 21, 2024 · 11 comments · Fixed by #14864
Closed

[CAL-3505] Issue with Webhooks (Meeting started/ended triggers) #14685

PeerRich opened this issue Apr 21, 2024 · 11 comments · Fixed by #14864
Assignees
Labels
api area: API, enterprise API, access token, OAuth 🐛 bug Something isn't working crm-apps area: crm apps, salesforce, hubspot, close.com, sendgrid High priority Created by Linear-GitHub Sync
Milestone

Comments

@PeerRich
Copy link
Member

PeerRich commented Apr 21, 2024

Hello!

Currently, after communicating with Zapier support, we have received information from them indicating that the error is likely on your side:

"We've checked the bug report filed for the Cal.com team and there is no update yet.

As Ian mentioned, I might suggest you check with the Cal.com support team, if there might be some settings in Cal.com or some differences with particular meetings that could be preventing Cal.com from sending these notifications to Zapier. "

The situation is as follows:

  • When scheduling a meeting, information is pulled from Calcom into our CRM ("Trial booked" status).
  • When canceling a meeting or successfully completing a meeting, information from Calcom is not pulled into our CRM (statuses "Canceled" and "Past").

That is, with the standard "Meeting Ended" event, information from Calcom is only transferred in 5-10% of cases.
Since April 14th, only 4 users have had information pulled: 1799211, 1777800, 1763228, 1763963.

Please verify the information and provide a response as soon as possible.

CAL-3505

@PeerRich PeerRich changed the title Issue with Zapier [CAL-3505] Issue with Zapier Apr 21, 2024
@dosubot dosubot bot added api area: API, enterprise API, access token, OAuth crm-apps area: crm apps, salesforce, hubspot, close.com, sendgrid 🐛 bug Something isn't working labels Apr 21, 2024
@capitanes
Copy link

Hello, do you have any idea about the approximate timeline for when you will be able to fix the bug? We have been waiting for a solution for over a month now. We have reached out to both Zapier and you, but there has been no result.

@milospuac
Copy link
Contributor

@CarinaWolli have you had the time to look into this?

@CarinaWolli
Copy link
Member

@CarinaWolli have you had the time to look into this?

I am actively looking into that, but was not able to identify the issue yet why not all of your bookings trigger your zap. I am still on it

@CarinaWolli CarinaWolli self-assigned this Apr 30, 2024
@PeerRich PeerRich added this to the v4.1 milestone Apr 30, 2024
@PeerRich PeerRich added the Medium priority Created by Linear-GitHub Sync label Apr 30, 2024
@CarinaWolli
Copy link
Member

@capitanes I found the issue why the 'meeting ended' trigger is not working all the time. I am working on a fix for it

@PeerRich PeerRich added High priority Created by Linear-GitHub Sync and removed Medium priority Created by Linear-GitHub Sync labels May 1, 2024
@PeerRich PeerRich changed the title [CAL-3505] Issue with Zapier [CAL-3505] Issue with Zapier (Meeting ended trigger) May 1, 2024
@PeerRich PeerRich changed the title [CAL-3505] Issue with Zapier (Meeting ended trigger) [CAL-3505] Issue with Webhooks (Meeting started/ended triggers) May 8, 2024
@keithwillcode keithwillcode modified the milestones: v4.1, v4.2 May 9, 2024
@capitanes
Copy link

capitanes commented May 13, 2024

Please, fix integration module "meeting ended" он Zapier, becouse its works with errors. https://prnt.sc/Hp9D6ZMJXb-Z

@CarinaWolli
Copy link
Member

Please, fix integration module "meeting ended" он Zapier, becouse its works with errors. prnt.sc/Hp9D6ZMJXb-Z

What error are you getting?

@capitanes
Copy link

When I want to receive a test event to set up integration, I receive events of type "booking" instead of "meeting ended," which results in me getting the wrong set of data and unable to set up the integration.
https://prnt.sc/C7hQLkdbsjcz

@CarinaWolli
Copy link
Member

When I want to receive a test event to set up integration, I receive events of type "booking" instead of "meeting ended," which results in me getting the wrong set of data and unable to set up the integration.

There is an issue open for that: #14776

Until then, you can still use any field that is coming in when the zap triggers. Here it's explained how to manually add variables: https://community.zapier.com/how-do-i-3/zapier-test-data-does-not-match-live-data-20869

@capitanes
Copy link

Thank you for the feedback. I'm glad the instructions helped with setting up the integration. However, we have noticed another issue with transmitting the "meeting ended" event through Zapier. Since my last message, 13 events have been completed in the Cal.com account, but none of them were transmitted to Zapier. There are no errors, they simply appear to be missing.

I can provide you with more information about the account if you contact me via email at ruslansungurov@gmail.com.

@capitanes
Copy link

@CarinaWolli Hello. Could you give me some guidance on the timing of solving the problem I mentioned above?

Yesterday, some data about "meeting ended" was transmitted through Zapier, but then it stopped being transmitted and has not been transmitted since then

@CarinaWolli
Copy link
Member

@capitanes this should be fixed in our next release, #14864 is not yet in production. We should have a release today or tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api area: API, enterprise API, access token, OAuth 🐛 bug Something isn't working crm-apps area: crm apps, salesforce, hubspot, close.com, sendgrid High priority Created by Linear-GitHub Sync
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants