How to Connect Microsoft Teams Calendars to OpenClaw in Slack

Why Connect Your Microsoft Teams Calendar to Your Slack AI Agent?

If your organization runs Microsoft 365, chances are your calendar lives in Teams or Outlook — but your day-to-day work coordination happens in Slack. That split creates friction. Your AI agent in Slack doesn't know you have a 2pm standup, can't automatically block focus time before a big deployment, and can't reschedule a meeting when a Linear incident fires at 11am.

Connecting your Microsoft Teams calendar to OpenClaw via SlackClaw closes that gap. Once the integration is live, your agent gains full awareness of your schedule and can act on it autonomously — cross-referencing GitHub PR reviews, Jira sprint deadlines, and Notion project timelines to make scheduling decisions that actually make sense in context.

This guide walks you through the exact steps to get that connection working, along with some practical examples of what you can do once it's set up.

Prerequisites

Before you start, make sure you have the following in place:

• A SlackClaw workspace with an active account (any credit tier works)
• Admin or delegated access to a Microsoft 365 account
• Your SlackClaw agent already deployed to your Slack workspace
• Optionally: other integrations like GitHub, Linear, or Gmail already connected, so the calendar agent has useful context to work with

SlackClaw runs on a dedicated server per team, which means your Microsoft credentials and calendar data never share infrastructure with other organizations. That matters when you're handing an AI agent access to sensitive scheduling information.

Step 1: Authorize the Microsoft 365 Integration

SlackClaw connects to Microsoft Teams calendars through the Microsoft Graph API, using OAuth 2.0. No API keys to copy, no service accounts to configure manually.

1. Open your SlackClaw dashboard and navigate to Integrations → Browse.
2. Search for Microsoft 365 or Microsoft Teams in the integration library. You'll see it listed alongside the 800+ other one-click connections available.
3. Click Connect. You'll be redirected to Microsoft's OAuth consent screen.
4. Sign in with your Microsoft 365 account and grant the requested permissions. At minimum, SlackClaw requests Calendars.ReadWrite and User.Read scopes.
5. After authorization, you'll be redirected back to your SlackClaw dashboard with a green confirmation status.

If your organization uses conditional access policies or requires admin consent for third-party apps, you may need your Microsoft 365 tenant admin to approve the app registration. In that case, share the SlackClaw OAuth app client ID with your admin and ask them to grant tenant-wide consent from the Azure Active Directory portal under Enterprise Applications.

Step 2: Verify the Connection in Slack

Once OAuth is complete, test the connection by messaging your SlackClaw agent directly in Slack:

@SlackClaw what does my calendar look like tomorrow?

The agent should respond with a structured summary of your events, pulled live from Microsoft Graph. If it returns an error, the most common causes are:

• The OAuth token didn't save — try disconnecting and reconnecting from the dashboard
• Your account requires MFA re-authentication — sign into Microsoft 365 manually to refresh the session
• Calendar sharing permissions are restricted at the tenant level — confirm with your IT admin that Calendars.ReadWrite is not blocked by a policy

Step 3: Configure Calendar Permissions for the Agent

By default, the agent has read and write access to your primary calendar. You can scope this down — or expand it to include shared team calendars — from the integration settings. Learn more about our integrations directory.

Reading Shared Team Calendars

If your team uses a shared Microsoft Teams calendar (common for tracking sprint ceremonies, on-call rotations, or release windows), you can grant the agent access to those as well. Learn more about our pricing page.

1. In SlackClaw dashboard, go to Integrations → Microsoft 365 → Settings.
2. Under Calendar Access, click Add Calendar.
3. Enter the shared calendar's email address or display name. For Teams-managed calendars, this is typically the Microsoft 365 Group email.
4. Save. The agent will now be able to read and (if you enable it) write to that calendar.

Restricting Write Access

If you'd prefer the agent only reads your calendar rather than creating or modifying events autonomously, toggle Read-only mode in the same settings panel. You can always upgrade this later once you're confident in the agent's scheduling behavior.

Step 4: Build Useful Automations

This is where things get genuinely powerful. Because SlackClaw's OpenClaw agent has persistent memory and context, it doesn't just answer one-off calendar questions — it builds an understanding of your rhythms over time and uses calendar data as one layer in multi-tool reasoning.

Automatic Meeting Prep Briefs

Ask your agent to send you a prep brief in Slack 30 minutes before any meeting that has an associated Notion doc or Jira ticket:

@SlackClaw before any meeting with "Sprint Review" or "Planning" in the title,
pull the current sprint from Jira and the relevant Notion page and send me
a 3-bullet summary 30 minutes before it starts.

The agent will store this as a persistent instruction and execute it automatically going forward — no cron jobs, no Zapier chains.

Conflict Detection Across Tools

One of the most practical uses: asking the agent to flag scheduling conflicts before they become problems.

@SlackClaw if any GitHub PR review is assigned to me and the review window
overlaps with a meeting block, ping me in Slack and suggest the next
available 30-minute focus slot.

Because the agent holds context across your GitHub, Microsoft calendar, and Slack simultaneously, it can reason across all three without you having to manually check each system.

Creating Events from Slack Conversations

You can also instruct the agent to create calendar events directly from Slack threads. For example, if a conversation in #engineering concludes with an action item to sync on a bug:

@SlackClaw schedule a 30-minute call between me and @dana to discuss the
auth regression. Find a slot this week where we're both free.

The agent will check both calendars (if Dana has also connected their Microsoft 365 account), find an open window, and create the event — including a link back to the Slack thread in the event description.

Step 5: Layer in Other Integrations for Full Context

The Microsoft Teams calendar integration becomes significantly more useful when combined with other tools your team already uses. SlackClaw's 800+ integrations mean the agent can pull context from anywhere that's relevant to a scheduling decision.

Some high-value combinations:

• Linear + Calendar: Automatically block focus time when high-priority issues are assigned to you
• Gmail + Calendar: Parse email threads for meeting requests and add them to your Teams calendar without leaving Slack
• GitHub + Calendar: Notify you when a release is tagged and suggest blocking your calendar for a post-deploy monitoring window
• Notion + Calendar: Attach relevant project docs to calendar events based on title keywords

Each of these follows the same one-click OAuth pattern. Once connected, the agent weaves them together without you having to write orchestration logic. For related insights, see Sync Google Calendar with OpenClaw in Slack.

A Note on Pricing and Usage

Calendar automations that run on a schedule — like that meeting prep brief — do consume credits each time they execute. SlackClaw's credit-based pricing means you're paying for actual agent activity, not per-seat licenses. A small team running a handful of calendar automations daily will typically use a modest number of credits per month, and you can monitor usage from the dashboard to stay on top of it.

Tip: If you're running automations across a large shared calendar with dozens of daily events, consider scoping the agent's trigger conditions narrowly (e.g., only meetings with specific keywords) to keep credit usage predictable.

Troubleshooting Common Issues

Agent Returns Stale Calendar Data

Microsoft Graph tokens expire. If the agent's calendar data seems outdated, go to Integrations → Microsoft 365 and click Refresh Token. This re-authenticates without requiring full re-authorization.

Events Created by Agent Don't Appear in Teams

Confirm the calendar write permission is granted and that you're not in read-only mode. Also check that the Microsoft 365 account connected is the same one your Teams client is signed into — mismatched accounts are a frequent source of confusion.

Shared Calendar Not Visible

The Microsoft 365 account must have been explicitly granted access to the shared calendar by its owner. Verify this in Outlook Web Access before trying to add it in SlackClaw. For related insights, see Use OpenClaw for Async Communication in Slack.

What's Next

Once your Microsoft Teams calendar is connected and you've run a few automations, the natural next step is building custom skills that encode your team's specific workflows. SlackClaw lets you define reusable agent behaviors — for example, a Sprint Kickoff skill that pulls the new sprint from Linear, blocks focus time on everyone's calendar, and posts a summary to #engineering — all triggered by a single Slack message.

Calendar awareness is a foundational layer. Once the agent knows when you work, what's scheduled, and what matters, it stops being a reactive Q&A tool and starts functioning as a genuine scheduling and coordination partner inside the tools you already use every day.