Authorize an Outlook account through Composio so Linkence can read current calendars, meetings and availability live. Create, update and cancel tools stay disabled until enabled by the user, and every execution requires approval in chat.
Outlook Calendar connects through an admin-defined boundary. Each object type below lists what Linkence reads, the scope condition that applies and the limitation you should know about before the first sync. Your Outlook Calendar account remains the system of record.
Current calendars, events, times and locations
Connected accountAttendees, organisers and response state
Requested calendar operationFree and busy windows
Bounded requested time rangeFind · Prepare · Act
Pair Outlook Calendar with Outlook, Microsoft Teams, Sharepoint and the answer stops being a search result. Evidence arrives from every connected system, and the next step waits for your approval.
A current meeting list with normalized attendee and timing details
Prepare an approved event changeBring one of these to the demo on representative data. Every answer arrives with citations that open the original Outlook Calendar record.
Every answer reflects the verified connector behaviour, never generalised.
Live reads from the user's connected Microsoft account; Bounded event and availability queries; Per-execution approval for every enabled write.
Indexing calendar events into the Knowledge Bank; Automatic scheduling without approval; Accounts the signed-in user has not authorized.
Live fetch from the connected Microsoft account. Scope: User-authorized Outlook Calendar account.
Only verified, approval-gated writes: create an approved calendar event; update an approved event; cancel an approved event. Every sensitive change is prepared, policy-checked and held for a person before execution.
We will show how Linkence finds the relevant context, presents the work and keeps every sensitive change under your team's control.
Representative data is enough for the first demo. No production access required.