MULTI-APP TOOLKIT
Build with GitHub + Salesforce
- Multi-app
- One MCP session
- 109 actions
- 39 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitHub and Salesforce 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,salesforce_rest_api",
},
},
},
)
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 Salesforce 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, salesforceRestApiTools] =
await Promise.all([
pd.components.list({ app: "github" }),
pd.components.list({ app: "salesforce_rest_api" }),
])
// 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=salesforce_rest_api" \
-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
Salesforce
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
Salesforce tools
The Salesforce tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 61
-
Add Contact to Campaign
actionAdd an existing contact to an existing campaign as a campaign member. Use Find Records onContactand onCampaignto look up the two IDs first. The contact must already exist - use Create Contact if it does not. See the documentationWritev0.1.9 -
Add Lead to Campaign
actionAdd an existing lead to an existing campaign as a campaign member. Use Find Records onLeadand onCampaignto look up the two IDs first. The lead must already exist - use Create Lead if it does not. See the documentationWritev0.1.9 -
Convert SOAP XML Object to JSON
actionConvert a SOAP XML payload received from Salesforce into JSON. Use this on the raw body delivered by an outbound-message trigger; it makes no API call. Every other Salesforce action already returns JSON, so this is only needed for outbound-message workflows. See the documentationRead-onlyv0.0.13 -
Create Account
actionCreate a Salesforce account (a company or organization record). Use Describe Object onAccountto discover which fields your org requires before calling. For example,NameAcme Corpcreates a minimal account and returns its new record ID. See the documentationWritev0.4.1 -
Create Accounts (Batch)
actionCreate many Salesforce accounts in one job using Bulk API 2.0. Use this instead of Create Account when inserting more than roughly 200 records - it is asynchronous and returns a job ID, not the created records. Poll the job in Salesforce to confirm completion; a successful response means the job was accepted, not that every row loaded. Input is a CSV file - supply a path under/tmpor a URL to download it from, with a header row of Salesforce field API names. See the documentationWritev0.0.8 -
Create Attachment
actionAttach a file to an existing Salesforce record (classicAttachmentobject). Use Find Records to get the parent record ID first. For newer orgs prefer Salesforce Files - use Insert Blob Data withContentVersioninstead. See the documentationWritev0.6.1 -
Create Campaign
actionCreate a Salesforce marketing campaign. Use Add Contact to Campaign or Add Lead to Campaign afterwards to populate its members. For example,Name: "Summer 2026 Webinar"creates the campaign and returns its ID. See the documentationWritev0.3.9 -
Create Case
actionCreate a Salesforce support case (a customer issue or request). Use List Cases to check whether a matching case already exists before creating a duplicate. After creating, use Create Case Comment to add notes or List Case Feed Items to read its activity. See the documentationWritev1.0.1
Triggers top 4 of 12
-
Case Updated (Instant, of Selectable Type)
triggerEmit new event when a case is updated. See the documentationv0.0.13 -
Email Template Updated (Instant, of Selectable Type)
triggerEmit new event when an email template is updated. See the documentationv0.0.13 -
Knowledge Article Updated (Instant, of Selectable Type)
triggerEmit new event when a knowledge article is updated. See the documentationv0.0.13 -
New Case (Instant, of Selectable Type)
triggerEmit new event when a case is created. See the documentationv0.0.13
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,salesforce_rest_api
- Primary app
- GitHub (github)
- Second app
- Salesforce (salesforce_rest_api)
- Authentication
- OAuth + OAuth
- Available actions
- 109
- Available triggers
- 39