MULTI-APP TOOLKIT
Build with GitHub + Intercom
- Multi-app
- One MCP session
- 61 actions
- 43 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitHub and Intercom 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,intercom",
},
},
},
)
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 Intercom 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, intercomTools] =
await Promise.all([
pd.components.list({ app: "github" }),
pd.components.list({ app: "intercom" }),
])
// 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=intercom" \
-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
Intercom
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
Intercom tools
The Intercom tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 13
-
Add Tag To Contact
actionAdds a specific tag to a contact in Intercom. Use Search Contacts to find the contact's ID and List Tag ID Options to find valid tag IDs before calling this action. Example: set Contact ID to63a07ddf05a32042dffac965and Tag ID to7522907to tag that contact. Returns the updated tag object on success. See the documentation.Writev0.0.5 -
Create Note
actionCreates a note on a contact's record in Intercom. The note is automatically attributed to the currently authenticated admin — no Admin ID prop is required. Use Search Contacts to find the contact's ID before calling this action. Example: set User to63a07ddf05a32042dffac965and Body toFollowed up via email on 2024-01-15to log a note on that contact. Returns the new note object includingid,body, andauthor. See the documentationWritev0.0.9 -
List Admin ID Options
actionRetrieves all admins in your Intercom workspace and returns their IDs and names. Call this action before any action that requires an Admin ID — such as Manage A Conversation, Reply To Conversation, or Send Message To Contact — to discover valid values. Example: returns[{ label: "Jane Doe", value: "25" }, ...]. See the documentation.Read-onlyv0.0.3 -
List Assignee ID Options
actionRetrieves all teams in your Intercom workspace and returns their IDs and names. Call this action before Manage A Conversation to discover valid team IDs for conversation assignment. Example: returns[{ label: "Support", value: "334" }, ...]. Use0to represent Unassigned. See the documentation.Read-onlyv0.0.3 -
List Conversations
actionLists conversations in your Intercom workspace, most recently updated first (GET /conversations). Use this to discover a conversation's ID before calling Reply To Conversation, Manage A Conversation, or Retrieve Conversation — there is no other way to look one up. Returns a bounded page of conversations, each includingid,state,created_at, and the latest message part. Ifpages.next.starting_afteris present in the response, call this action again with that cursor in Starting After to retrieve the next page. Pass Fields (e.g.["id", "state", "created_at"]) to limit each returned conversation to only those keys. Example: leave all props empty to fetch the 20 most recently updated conversations. See the documentation.Read-onlyv0.0.2 -
List Tag ID Options
actionRetrieves all tags in your Intercom workspace and returns their IDs and names. Call this action before Add Tag To Contact to discover valid tag IDs. Example: returns[{ label: "VIP", value: "7522907" }, ...]. See the documentation.Read-onlyv0.0.3 -
Manage A Conversation
actionClose, snooze, open, or assign a conversation by its ID. Which of the optional props apply depends on Message Type:closeuses Body,snoozeduses Snoozed Until,assignmentuses Type together with Assignee ID or Team Assignee ID, andopenuses none of them. Example: set Conversation ID to192783634529321, Message Type toclose, and Body toIssue resolvedto close that conversation with a closing comment. See the documentation.Writev0.1.2 -
Reply To Conversation
actionReply to an existing Intercom conversation as an admin or on behalf of a contact (POST /conversations/{conversation_id}/reply). Use List Admin ID Options to find a valid Admin ID, and Search Contacts to find a contact's Intercom user ID, email, or external user ID. Example: set Conversation ID to192783634529321, Reply Type toadmin, Message Type tocomment, Body toThanks for reaching out!, and Admin ID to25to post that comment as an admin reply. See the documentation.Writev0.1.1
Triggers top 4 of 16
-
New Companies
triggerEmit new event each time a new company is added.v0.0.9 -
New Reply From Admin
triggerEmit new event each time an admin replies to a conversation.v0.0.9 -
New Conversations
triggerEmit new event each time a new conversation is added.v0.0.9 -
New Reply From User
triggerEmit new event each time a user replies to a conversation.v0.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,intercom
- Primary app
- GitHub (github)
- Second app
- Intercom (intercom)
- Authentication
- OAuth + OAuth
- Available actions
- 61
- Available triggers
- 43