Calendar Connections
Calendaria connects to Google Calendar and Microsoft Outlook. Connect one or more accounts, then use web chat, Telegram, WhatsApp, or MCP to read your schedule and prepare confirmed calendar changes.
Google and Outlook
The dashboard can connect multiple calendar accounts. Calendaria can work with calendars visible inside those accounts and can mark one account as the default for new events.
- 1Select Connect Google Calendar or Connect Microsoft (Outlook) in the dashboard.
- 2Approve the calendar permissions requested by the provider.
- 3Return to Calendaria and confirm the card shows the connected account.
What Calendaria can access
When connected, Calendaria can read and write events through the provider calendar API. This lets the assistant list events, open event details, create events, move or edit events, delete events, respond to invitations, find free time, and warn about conflicts across calendars it can access.
Calendar questions run now
Requests such as what do I have tomorrow? execute immediately because they do not mutate events.
Changes wait for confirmation
Create, move, edit, delete, and RSVP requests are prepared as pending actions before Calendaria writes to your calendar.
Busy slots are surfaced
When a create or move request conflicts, Calendaria can warn you and suggest alternatives before confirmation.
Connected accounts
Calendaria supports multiple connected calendar accounts per Calendaria user. Each account may contain multiple calendars, such as personal, work, family, or shared calendars. The dashboard lists connected accounts and marks one account as the default for new writes.
Provider note
Google Calendar and Microsoft Outlook are supported today. Apple Calendar, CalDAV, and deeper provider federation remain roadmap items. Outlook attendee free/busy is a current limitation: Calendaria reports unavailable attendee checks as unchecked instead of assuming they are free.
Availability and conflicts
Calendaria can search for open time across connected calendars included in availability checks.
find 45 minutes this week for a planning session
find a time that works for me and ana@example.com tomorrow
When attendee availability cannot be verified, Calendaria should say so rather than imply the slot works for everyone.
For create and move requests, Calendaria checks conflicts before the write. A conflict warning does not block the action automatically; it gives you the warning, possible alternatives, and confirmation controls so you decide.
Invitation responses
Calendaria can respond to calendar invitations for the connected account:
accept the design review
decline tomorrow's lunch
mark the team sync as maybe
For recurring invitations, Calendaria can respond to one occurrence or the full series when you explicitly ask for all occurrences. RSVP changes require confirmation.
Booking-link availability
Booking links use a related availability model: Calendaria shows guests computed free slots, not calendar details. Booking and group invite public-link flows currently use Google calendar connections.
The booked event is created on the account/calendar attached to that booking link.
Target a specific calendar
When a request mentions an account or calendar name, Calendaria can use that as the target if the account is connected and the calendar is visible and writable. If no target is named, reads may search across connected accounts and writes use the default account/calendar.
put my son's doctor appointment tomorrow at 3pm in my family calendar
schedule budget review Friday in my work calendar
what is on the family calendar this weekend?
If the account or calendar name is ambiguous, read-only, or not visible from a connected account, Calendaria may ask you to clarify or choose another writable calendar.
Revoke access
You can disconnect an account from the dashboard or revoke Calendaria's access from the provider's security settings. If you disconnect the default account, Calendaria promotes another active account as the default for new writes when one is available.
Troubleshooting
If calendar requests fail after connecting a calendar:
- confirm that the dashboard shows a calendar provider as connected
- make sure the intended account is connected
- reconnect if an account needs fresh permissions
- try a simple read command before sending a write request