v2.6.27Latest

This release fixes calendar bots for Microsoft Teams channel meetings, which failed to join because the bot was sent to the channel link in the invite instead of the meeting join link. If you record Teams meetings from connected calendars, those bots now join. Creating a bot with a Teams channel, team or chat link is now rejected up front, because those links never lead to a meeting.

💥Breaking Changes

• Teams channel, team and chat links are rejected at bot creation. POST /v2/bots, batch bot creation and scheduled bots now return 400 with FST_ERR_INVALID_MEETING_PLATFORM for teams.microsoft.com/l/channel/…, /l/team/… and /l/chat/… links. Who is affected: integrations that pass a Teams link copied from a channel or chat rather than from the meeting itself. These requests used to be accepted, but the bot could never join and the bot ended with BOT_REMOVED_TOO_EARLY. What to do: send the meeting's join link (teams.microsoft.com/meet/… or teams.microsoft.com/l/meetup-join/…), see Create bot.

🐛Bug Fixes

• Calendar bots now join Microsoft Teams channel meetings. Invites for meetings scheduled in a Teams channel list the channel link before the join link, and the channel link was used as the event's meeting_url. The bot opened the channel instead of the meeting and ended with BOT_REMOVED_TOO_EARLY. Calendar events now use the meeting's join link. To refresh upcoming events right away, call POST /v2/calendars/{calendar_id}/sync, see Calendars.

↩ All releases