Calendar V2 FAQ

Calendar V2 FAQ

Grouping recurring calendar events

You may want to group all instances of a recurring event for tracking and applying recording preferences on these events.

If you're using the Calendar V2 integration, we recommend using these fields to group instances of a recurring events:

  • seriesMasterId - Microsoft Outlook
  • recurringEventId - Google Calendar

Since these are calendar platform-specific, you can find them in the raw attribute of the calendar event object.

What if multiple bots from different apps using Recall try to join the same meeting?

Deduplication keys are scoped to a given Recall account. This means that multiple bots should have no trouble joining the same meeting, even if both companies are using the same deduplication key scheme.

Why is the platform_email null when I create the calendar?

The ​platformΒ­_email​ may be ​null​ briefly when you create the calendar. This is because the calendar sync (which populates the ​platformΒ­_email​) happens asynchronously after the calendar is created.

If you need the email immediately, we'd recommend using the OAuth token to call the calendar platform (Google or Microsoft) APIs directly to retrieve the user email.

Why did a calendar fail to connect with an invalid_scope error?

Calendars can fail to connect due to invalid_scope for one of two reasons:

  1. The OAuth client is setup incorrectly (e.g. missing necessary scopes in the OAuth client setup)
  2. The end user did not grant the necessary permissions when connecting their account. This can happen when they forget to click a checkbox during the OAuth flow.
If a user doesn't click the highlighted checkbox, this can result in an `invalid_scope` error on their calendar.

If a user doesn't click the highlighted checkbox, this can result in an invalid_scope error on their calendar.