MULTI-APP TOOLKIT
Build with Microsoft 365 Planner + Microsoft Outlook Calendar
- Multi-app
- One MCP session
- 21 actions
- 7 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Microsoft 365 Planner and Microsoft Outlook Calendar tool at once — connect once, list tools, and call them like any single-app session.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "microsoft_365_planner,microsoft_outlook_calendar",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Microsoft 365 Planner and Microsoft Outlook Calendar tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Bucket:
const result = await mcp.callTool({
name: "microsoft_365_planner-create-bucket",
arguments: {
groupId: "Group",
planId: "Plan",
},
})import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [microsoft365PlannerTools, microsoftOutlookCalendarTools] =
await Promise.all([
pd.components.list({ app: "microsoft_365_planner" }),
pd.components.list({ app: "microsoft_outlook_calendar" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=microsoft_365_planner" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=microsoft_outlook_calendar" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
Microsoft 365 Planner
Connected account
Microsoft Outlook Calendar
Connected account
TOOLS
Microsoft 365 Planner tools
The Microsoft 365 Planner tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create Bucket
actionCreate a new bucket in Microsoft 365 Planner. See the documentationWritev0.0.5 -
Create Plan
actionCreate a new plan in Microsoft 365 Planner. See the documentationWritev0.0.5 -
Create Task
actionCreate a new task in Microsoft 365 Planner. See the documentationWritev0.0.5 -
List User Tasks
actionList all user tasks in Microsoft 365 Planner. See the documentationRead-onlyv0.0.4 -
Update Task
actionUpdates a task in Microsoft 365 Planner. See the documentationWritev0.0.5
Triggers
-
New Plan Created
triggerEmit new event when a new Plan is created in Microsoft 365 Plannerv0.0.4 -
New Task Assigned to User
triggerEmit new event when a Task is assigned to the authenticated user in Microsoft 365 Planner. See the documentationv0.0.3 -
New Task Created
triggerEmit new event when a new Task is created in Microsoft 365 Plannerv0.0.4
TOOLS
Microsoft Outlook Calendar tools
The Microsoft Outlook Calendar tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 16
-
Accept Event
actionAccept a calendar event invitation and optionally send a response to the organizer. Use List Events or Get Event to find the event ID. See the documentationWritev0.0.2 -
Create Calendar Event
actionCreate an event in the user's default calendar. Supports one-time and recurring events. See the documentation and recurring event example.Writev0.0.16 -
Decline Event
actionDecline a calendar event invitation and optionally propose an alternate time. Use List Events or Get Event to find the event ID. To propose a new time, passproposedNewTimeas a JSON string withstartandendobjects (each withdateTimein ISO 8601 format andtimeZoneas a Windows timezone name, e.g."Pacific Standard Time"). Alternate-time proposals are only valid when the event hasallowNewTimeProposals: trueandsendResponseistrue. See the documentationWritev0.0.2 -
Delete Calendar Event
actionDelete an event in the user's default calendar. See the documentationWritev0.0.11 -
Delete Recurring Event Instance
actionDelete an individual instance of a recurring event in the user's default calendar. See the documentationWritev0.0.8 -
Find Meeting Times
actionSuggest meeting times and locations based on organizer and attendee availability. See the documentationRead-onlyv0.0.3 -
Get Current User
actionReturns the authenticated Microsoft user's ID, display name, email, and principal name via Microsoft Graph. Call this first when the user says 'my calendar', 'my events', or needs to identify themselves as organizer/attendee. Useidormailto filter results from List Events or set the organizer in Create Calendar Event. See the documentation.Read-onlyv0.0.5 -
Get Event
actionRetrieve a calendar event by its Microsoft Graph event ID. Pass theidfrom List Events when you need full details (for examplebody,attendees, orrecurrence) that list responses may omit or truncate. See the documentationRead-onlyv0.0.4
Triggers
-
Calendar Event Deleted (Instant)
triggerEmit new event when a Microsoft Outlook Calendar event is deleted. Because deleted events cannot be re-fetched from the Outlook API after deletion, this trigger emits notification metadata only (not the full event object). The emitted payload includes the deleted event identifier (eventId),changeType,subscriptionId,tenantId, andnotificationTimestamp. Downstream processors must rely solely on this metadata. See the documentationv0.0.1 -
New Calendar Event (Instant)
triggerEmit new event when a new Calendar event is createdv0.0.16 -
New Calendar Event Update (Instant)
triggerEmit new event when a Calendar event is updatedv0.0.16 -
New Upcoming Calendar Event (Polling)
triggerEmit new event based on a time interval before an upcoming calendar event. See the documentationv0.0.9
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- microsoft_365_planner,microsoft_outlook_calendar
- Primary app
- Microsoft 365 Planner (microsoft_365_planner)
- Second app
- Microsoft Outlook Calendar (microsoft_outlook_calendar)
- Authentication
- OAuth + OAuth
- Available actions
- 21
- Available triggers
- 7