MULTI-APP TOOLKIT
Build with GitHub + monday
- Multi-app
- One MCP session
- 66 actions
- 37 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitHub and monday 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,monday",
},
},
},
)
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 monday 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, mondayTools] =
await Promise.all([
pd.components.list({ app: "github" }),
pd.components.list({ app: "monday" }),
])
// 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=monday" \
-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
monday
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
monday tools
The monday tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 18
-
Create an Update
actionPost an update (a comment) on an item, or reply to an existing update. Use to add a note to an item's activity feed; this changes no column value — use Update Column Values for that. SetBoard ID,Item IDandUpdate Body, and setParent Update IDonly when replying to an existing update rather than starting a new thread. Example: Update BodyDesign approved, moving to build. Returns the new update's ID as a string. Use Get Board Items Page to find anItem ID. See the documentationWritev0.0.19 -
Create Board
actionCreate a new board in a workspace. Use when you need a new board before adding groups, columns or items to it. SetBoard NameandBoard Kind(public,privateorshare); if you omitWorkspace IDthe board is created in the Main Workspace. Example: Board NameQ3 Campaigns, Board Kindpublic. Returns the new board's ID as a string (e.g.2419687965), not the full board object — call List Boards if you need its details. Use List Workspace ID Options to find a validWorkspace ID. See the documentationWritev0.0.16 -
Create Column
actionAdd a column to an existing board. Use when a board is missing a field you need before setting values with Create Item or Update Column Values. SetBoard ID,TitleandColumn Type(e.g.status,text,date,numbers).Custom Labels (Defaults)is accepted only whenColumn Typeisstatusordropdownand is rejected for any other type. Example: TitlePriority, Column Typestatus, Custom Labels{ "1": "High", "2": "Low" }. Returns the new column's ID as a string (e.g.status_1). Call List Columns afterwards to confirm the ID and the labels it accepts. See the documentationWritev0.1.8 -
Create Group
actionCreate a group (a titled section of rows) on a board. Use when you need somewhere to put new rows before calling Create Item, which takes an optionalGroup ID. SetBoard IDandGroup Name. Example: Board ID2419687965, Group NameIn Progress. Returns the new group's ID as a string (e.g.new_group12345) — pass that value asGroup IDto Create Item. Use List Board ID Options to find a validBoard ID. See the documentationWritev0.0.17 -
Create Item
actionCreate an item (a row) on a board. Use for a top-level row; use Create Subitem for a row nested under an existing item. SetBoard IDandItem Name, and optionallyGroup IDandColumn Values. Call List Columns first to get the column IDs and the labels astatusordropdowncolumn accepts. Example: Item NameWebsite redesign, Column Values{ "status": "Working on it", "date4": "2026-09-02", "numbers": 42 }. SetItem Create Labelstotrueto allow missingstatus/dropdownlabels to be created, which requires permission to change the board structure. Returns the new item's ID as a string (e.g.9876543210). See the documentationWritev0.1.9 -
Create Subitem
actionCreate a subitem nested under an existing item. Use when the row belongs to a parent item; use Create Item for a top-level row. SetBoard ID(the parent item's board),Parent Item IDandItem Name. Gotcha: subitems live on a separate subitems board, soColumn Valuesmust use that board's column IDs — run List Columns against the subitems board, not the board selected here. Example: Item NameDraft copy, Column Values{ "status": "Done" }. Returns the new subitem's ID as a string. See the documentationWritev0.1.9 -
Get Board Items Page
actionList every item (row) on a board, following the API's cursor automatically so all pages are returned in a single call — you do not need to paginate. Use when you want the whole board; use Get Items By Column Value to filter server-side by one column, which is far cheaper on a large board. SetBoard ID, and optionallyQuery Paramsto filter or sort. Example: Query Params{ "rules": [{ "column_id": "status", "compare_value": ["Done"], "operator": "any_of" }] }. Returns an array of items withid,name,state, timestamps and column values. Gotcha: a large board returns every row in one response, so expect a slow call and a large payload. See the documentationRead-onlyv0.0.7 -
Get Column Values
actionRead the column values of one item. Use when you already have anItem IDand want its field values; use Get Items By Column Value to search for items by a value instead. SetBoard IDandItem ID; leaveColumn IDsempty to return every column, or pass specific column IDs from List Columns. Example: Item ID9876543210, Column IDs["status", "date4"]. Returns an array holding the item and acolumn_valuesarray of{ id, value }pairs, wherevalueis the column's display text when one exists and the raw JSON value otherwise. See the documentationRead-onlyv0.0.14
Triggers top 4 of 10
-
Column Value Updated (Instant)
triggerEmit new event when a column value is updated on a board. See the documentationInstantv0.0.15 -
Name Updated (Instant)
triggerEmit new event when an item's name is updated. See the documentationInstantv0.0.15 -
New Board Created
triggerEmit new event when a board is created in Monday. See the documentationv0.0.16 -
New Item Created (Instant)
triggerEmit new event when a new item is added to a board. See the documentationInstantv0.0.15
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,monday
- Primary app
- GitHub (github)
- Second app
- monday (monday)
- Authentication
- OAuth + API key
- Available actions
- 66
- Available triggers
- 37