Connect a calendar

BeAI separates Microsoft 365, Google and Progenda calendars so that each connection keeps its own rules.

Add a connection

1. Enable the skill for the relevant provider.
2. Choose Add connection.
3. Authorise BeAI with the provider or enter the requested information.
4. Select the calendars the bot can read or modify.
5. Add specific instructions if different calendars have different purposes.

Limit available calendars

The connected account may have access to more calendars than the bot. Add only the calendars it needs. Use Add another calendar to extend the selection without recreating the connection.

Renew a connection

BeAI attempts to renew compatible tokens automatically. If the status turns red, use the reconnect button: selected calendars and their instructions are preserved.

Test the complete journey

Ask the bot to:

1. find an available time;
2. suggest a slot;
3. confirm the information;
4. create the appointment;
5. repeat the date and time in the correct time zone.

Then verify the event directly in the relevant calendar.

Move an existing appointment

To move, postpone or reschedule an appointment, the bot follows a different path from a new booking:

1. it uses the exact identifier supplied by trusted workflow context or searches the original appointment period;
2. it identifies the exact event;
3. it checks the requested target slot;
4. it updates the existing event without creating a second one.

An event identifier and a calendar identifier are distinct values. Events returned by BeAI include both so they cannot be confused. For Microsoft 365, BeAI also resolves the event’s actual parent calendar before the update and enforces the permissions configured for that calendar.

When an outbound call receives a calendar_event_id in its trusted context, BeAI reinjects that exact value when the event is updated. This protects opaque Microsoft 365 identifiers from being altered during the call. The calendar identifier is also repaired when exactly one update-enabled calendar matches the connection; when the choice is ambiguous, BeAI does not select a calendar on the bot’s behalf.

If several events match or the original appointment cannot be found, the bot asks for clarification instead of creating a duplicate. For best results, include the event identifier in trusted workflow context or, when it is not available, the original date, time, contact name and appointment title.