MULTI-APP TOOLKIT
Build with GitHub + Microsoft Outlook Calendar
- Multi-app
- One MCP session
- 64 actions
- 31 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitHub 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": "github,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: GitHub and Microsoft Outlook Calendar tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create Issue:
const result = await mcp.callTool({
name: "github-create-issue",
arguments: {
repoFullname: "Repository",
title: "Title",
},
})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 [githubTools, microsoftOutlookCalendarTools] =
await Promise.all([
pd.components.list({ app: "github" }),
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=github" \
-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
GitHub
Connected account
Microsoft Outlook Calendar
Connected account
TOOLS
GitHub tools
The GitHub tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 48
-
Create Issue
actionCreate a new issue in a repository, optionally with labels, assignees, and a milestone. Provide the repository as anowner/repostring. Labels and assignees are passed by name/login (e.g.bug,octocat) — setting them requires push access to the repo. To comment on an existing issue instead, use Create Issue Comment; to change an existing issue, use Update Issue. See the documentationWritev0.4.3 -
Search Issues and Pull Requests
actionSearch issues and pull requests across GitHub using the issues-search query DSL. This is the escape hatch for finding items by keyword, state, label, author, or assignee when you don't already know the issue/PR number. Build thequeryfrom space-separated qualifiers:repo:owner/nameto scope to one repo (a barerepo:namewith no owner is auto-resolved to your own account),is:issue/is:pr,is:open/is:closed,label:bug,author:octocat,assignee:octocat,in:title/in:body, and free-text keywords. Example:repo:PipedreamHQ/pipedream is:issue is:open label:bug raptor. Returns matching items (each withnumber,title,state,labels,html_url); feed a result'snumberinto Get Issue, Get Pull Request, or Create Issue Comment. See the query syntaxRead-onlyv0.3.3 -
Create Branch
actionCreate a new branch in a repository, pointing at the tip of a source branch. Provide the repository as anowner/repostring, the newbranchName, and optionally thesourceBranchto branch from (defaults to the repository's default branch). Use Create or Update File Contents to add commits to the new branch, then Create Pull Request to open a PR. See the documentationWritev1.0.2 -
Create Gist
actionAllows you to add a new gist with one or more files. See the documentationWritev0.0.18 -
Create Issue Comment
actionAdd a comment to an existing issue or pull request (GitHub treats PRs as issues for comments, so the samenumberworks for both). Provide the repository as anowner/repostring, the issue/PR number, and the comment body. If you only know the issue/PR by title, call Search Issues and Pull Requests first to resolve its number. See the documentationWritev0.1.3 -
Create or Update File Contents
actionCreate a new file or overwrite an existing one in a repository with a single commit. Provide the repository as anowner/repostring, the filepath, the raw textcontent(passed as-is — do not base64-encode it yourself), and a commit message. If the file already exists on the target branch it is overwritten; the required blob SHA is resolved for you automatically. Defaults to the repository's default branch unlessbranchis set. See the documentationWritev1.0.3 -
Create Pull Request
actionOpen a pull request proposing to merge one branch into another within a repository. Provide the repository as anowner/repostring, theheadbranch (the source containing your changes) and thebasebranch (the target, e.g.main), plus a title. The head and base branches must already exist and differ. For a cross-fork PR, setheadtousername:branch. Use Create or Update File Contents to push changes to a branch before opening the PR. See the documentationWritev1.0.3 -
Create Pull Request Review
actionSubmit a review on a pull request: approve it, request changes, or leave a general comment. SeteventtoAPPROVE,REQUEST_CHANGES, orCOMMENT— abodyis required forREQUEST_CHANGESandCOMMENT. Optionally attach inlinecommentstied to specific lines of the diff. GitHub forbids approving your own pull request, so useCOMMENTto leave feedback on PRs you authored. Provide the repository as anowner/repostring and the PR number. Use Get Pull Request Files to find the file paths and lines to comment on, and Search Issues and Pull Requests withis:prto resolve the PR number from a title. See the documentationWritev0.0.3
Triggers top 4 of 27
-
New Branch Created
triggerEmit new event when a branch is created.Instantv1.0.16 -
New Card in Column (Classic Projects)
triggerEmit new event when a (classic) project card is created or moved to a specific column. For Projects V2 useNew Issue with Statustrigger. More information hereInstantv1.0.15 -
New Collaborator
triggerEmit new event when a collaborator is addedInstantv1.0.16 -
New Commit
triggerEmit new event when commits are pushed to a branchInstantv1.0.17
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
- github,microsoft_outlook_calendar
- Primary app
- GitHub (github)
- Second app
- Microsoft Outlook Calendar (microsoft_outlook_calendar)
- Authentication
- OAuth + OAuth
- Available actions
- 64
- Available triggers
- 31