MULTI-APP TOOLKIT
Build with Asana + GitHub
- Multi-app
- One MCP session
- 73 actions
- 41 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Asana and GitHub 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": "asana,github",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Asana and GitHub tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add Task To Section:
const result = await mcp.callTool({
name: "asana-add-task-to-section",
arguments: {
task: "Task",
section_gid: "Section GID",
},
})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 [asanaTools, githubTools] =
await Promise.all([
pd.components.list({ app: "asana" }),
pd.components.list({ app: "github" }),
])
// 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=asana" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=github" \
-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
Asana
Connected account
GitHub
Connected account
TOOLS
Asana tools
The Asana tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 25
-
Add Task To Section
actionMoves a task into a specific section within an Asana project, removing it from any other section it currently occupies in that project. Use Search Sections to find the section GID and Search Tasks to find the task GID. Returns an empty object{}on success. Example: call withproject: '1204567890123456',task: '1202345678901234',section_gid: '1203456789012345'→ task is moved into that section and returns{}. See the documentationWritev1.0.0 -
Create Project
actionCreates a new project in an Asana workspace or team. Use this to set up a new initiative, sprint, or work stream. For organization workspaces you must supply ateamGID (use List Teams to find it). Returns the new project record including itsgid. Example: call withprojectName: 'Q4 Marketing Campaign',workspace: '1200123456789012',team: '1203456789012345',defaultView: 'board'→ returns{gid: '1204567890123456', name: 'Q4 Marketing Campaign'}. See the documentationWritev1.0.0 -
Create Subtask
actionCreates a new subtask nested under an existing parent task. Use this when the work is a sub-item of another task; for top-level tasks use Create Task. The parent task GID is required. Returns the new subtask record including itsgid. Example: call withtask_gid: '1202345678901234',subtaskName: 'Write first draft',due_on: '2026-10-05'→ returns{gid: '1207890123456789', name: 'Write first draft', resource_type: 'task'}. See the documentationWritev1.0.0 -
Create Task
actionCreates a new task in Asana. Use this to add a standalone task to a workspace or project. For subtasks, use Create Subtask instead; for template-based tasks, use Create Task from Template. Returns the new task record including itsgid. Example: call withtaskName: 'Review Q3 report',workspace: '1200123456789012',due_on: '2026-10-01'→ returns{gid: '1202345678901234', name: 'Review Q3 report', resource_type: 'task'}. See the documentationWritev1.0.0 -
Create Task Comment
actionAdds a comment (story) to an existing Asana task. Use this to post a text update or pinned note visible to task followers. Provide eithertext(plain text) orhtml_text(HTML-formatted), but not both. Returns the new story record including itsgidandtype. Example: call withtask_gid: '1202345678901234',text: 'Approved — ready to ship!'→ returns{gid: '1209012345678901', type: 'comment', text: 'Approved — ready to ship!'}. See the documentationWritev1.0.0 -
Create Task from Template
actionCreates a new Asana task by instantiating an existing task template. Use this when a team has a reusable task structure (e.g. a bug-report or onboarding template); for ad-hoc tasks use Create Task. Use List Task Templates to find the template GID. This kicks off an asynchronous job — the response is a job resource, not the finished task;new_task.gidis available immediately but the task's fields may still be populating, so use Find Task by ID if you need to confirm it's ready. The new task's project and memberships are determined by the template itself, not by any project passed here. Example: call withtaskTemplateId: '1205678901234567',name: 'Bug: Login page crash'→ returns{gid: '1205555555555555', resource_type: 'job', new_task: {gid: '1206789012345678'}}. See the documentationWritev1.0.0 -
Delete Task
actionDeletes an Asana task. This moves the task to the deleting user's trash and removes it from active views immediately; it can be recovered for 30 days before Asana permanently removes it. Use Find Task by ID to confirm the task GID before deleting. Returns an empty data object{}on success. Example: call withtask_gid: '1202345678901234'→ returns{}. See the documentationWritev1.0.0 -
Find Task by ID
actionRetrieves the complete record for a single Asana task by its GID. Use this to fetch full task details (description, assignee, due date, custom fields) after obtaining a task GID from Search Tasks. UseoptFieldsto request additional fields not returned by default. Example: call withtask_gid: '1202345678901234',optFields: ['due_on','assignee','custom_fields']→ returns the full task record for that GID. See the documentationRead-onlyv1.0.0
Triggers top 4 of 14
-
New Project Added To Workspace (Instant)
triggerEmit new event for each new project added to a workspace.Instantv0.1.15 -
New Story Added To Project (Instant)
triggerEmit new event for each story added to a project.Instantv0.1.15 -
New Subtask (Instant)
triggerEmit new event for each subtask added to a project.Instantv1.0.15 -
New Completed Task (Instant)
triggerEmit new event for each task completed in a project.Instantv0.1.15
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
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
- asana,github
- Primary app
- Asana (asana)
- Second app
- GitHub (github)
- Authentication
- OAuth + OAuth
- Available actions
- 73
- Available triggers
- 41