What an agent can do in Microsoft Calendar
Read calendars and create events.
Jobs on Rush that use Microsoft Calendar
- Are Next Week's Viewings Ready to Go? A Property Management App's Check of Each Leasing Agent's Outlook Calendar
- How Does Time-Tracking Software Draft Each Consultant's Weekly Timesheet From Their Microsoft Calendar?
- Which Managed IT Clients Are Due a Quarterly Business Review? Read It From Outlook Calendar
- Propose Interview Times From Each Recruiter's Microsoft 365 Calendar
Agents that use Microsoft Calendar
How Microsoft Calendar connects
Microsoft Calendar is a built-in app: you sign in with your Microsoft account on its own page, through Rush's own app, so you register no OAuth app. The sign-in asks only for the scopes listed below, and the run's token reaches graph.microsoft.com, Microsoft Graph calendars.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names microsoft-calendar in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
Scopes the sign-in asks for:
openidprofileemailoffline_accesshttps://graph.microsoft.com/User.Readhttps://graph.microsoft.com/Calendars.ReadWrite
POST https://api.phoenix.so/me/connections
{
"type": "app",
"name": "microsoft-calendar"
}Whose Microsoft Calendar account the agent uses
Your Microsoft Calendar connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Microsoft Calendar, and a run started with an API key uses the Microsoft Calendar of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Microsoft Calendar, and that agent's runs use their account and nothing else: never yours, never another user's.
More Productivity integrations
Frequently asked questions
How do I connect Microsoft Calendar to Rush?
Open Settings → Connections in the console and connect Microsoft Calendar, or send POST /me/connections with {"type":"app","name":"microsoft-calendar"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Microsoft Calendar account?
No. A run gets your Microsoft Calendar connection only when it names it in connections ("connections": ["microsoft-calendar"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Microsoft Calendar?
Read calendars and create events. 4 published jobs use it; this page lists them.
Can my app's users connect their own Microsoft Calendar?
Yes. Make each user an agent from your template, and they sign in to their own Microsoft Calendar through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for operations teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to