MULTI-APP TOOLKIT
Build with GitLab + Notion
- Multi-app
- One MCP session
- 53 actions
- 19 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitLab and Notion 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": "gitlab,notion",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: GitLab and Notion tools arrive
// together, each keyed by its own app's slug.
// e.g. run Approve Merge Request:
const result = await mcp.callTool({
name: "gitlab-approve-merge-request",
arguments: {
projectId: "Project",
mergeRequestIid: 10,
},
})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 [gitlabTools, notionTools] =
await Promise.all([
pd.components.list({ app: "gitlab" }),
pd.components.list({ app: "notion" }),
])
// 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=gitlab" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=notion" \
-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
GitLab
Connected account
Notion
Connected account
TOOLS
GitLab tools
The GitLab tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 28
-
Approve Merge Request
actionApprove a merge request as the authenticated user, or withdraw an earlier approval by setting Action tounapprove. Call Get Merge Request first to check the merge request is actually ready — itsreadinessrollup reports the pipeline status, conflicts and how many approvals are still required — and Get Merge Request Diffs to read the changes being approved. Two things commonly go wrong: GitLab refuses to let you approve your own merge request, and a project may require approval from a specific approval rule that the authenticated user does not satisfy; both surface as a401. To approve as part of leaving review feedback in one step, use Create Merge Request Review with its Action set toapproveinstead. Optionally pass SHA to make the approval conditional on the merge request's head commit, so it fails rather than silently approving work that was pushed after you read the diff. See the documentationWritev0.0.1 -
Create Branch
actionCreate a new branch in the repository. See the documentationWritev0.3.4 -
Create Epic
actionCreates a new epic. See the documentationWritev0.0.6 -
Create issue
actionCreates a new issue. See the documentationWritev0.2.4 -
Create Merge Request
actionOpen a new merge request from one branch into another. Use this for "open an MR", "raise a merge request", "submit my branch for review". Both branches must already exist in the project — use List Repo Branches to check, or Create Branch to make one. Reviewers and assignees are given as usernames and resolved to IDs automatically; a username that is not a member of the project is rejected rather than silently dropped. Set Draft totruefor work that is not ready for review — GitLab expresses this by prefixing the title withDraft:, which this action does for you and which blocks merging until removed. After creating, use Get Merge Request to check its pipeline and merge readiness. See the documentationWritev0.0.1 -
Create Merge Request Comment
actionPost a comment on a merge request. It works in three modes, chosen by which props you set: leave File Path and Discussion ID blank for a plain comment on the merge request as a whole; set File Path plus a line number to open an inline thread anchored to that line of the diff; or set Discussion ID to reply inside an existing thread. Use Get Merge Request Diffs first to get valid file paths and line numbers, and List Merge Request Discussions to get a Discussion ID to reply to. Line numbers follow GitLab's diff rules: for a line the merge request adds or leaves unchanged, pass New Line; for a line it removes, pass Old Line; for an unchanged context line, pass both. Getting that wrong is the usual cause of a rejected inline comment. To post several review comments at once, and optionally approve in the same step, use Create Merge Request Review instead. See the documentationWritev0.0.1 -
Create Merge Request Review
actionSubmit a whole review on a merge request in one step: any number of inline comments anchored to lines of the diff, an overall summary comment, and optionally an approval. This is the tool for "review this MR" — call Get Merge Request and Get Merge Request Diffs first to read the changes, then send the findings back here. GitLab has no single submit-review API, so this action posts each inline comment as its own thread and then approves if asked; if an individual comment is rejected (usually a line that is not part of the diff) the rest are still posted and the failures are returned infailed, so check that array rather than assuming everything landed. Line numbers follow GitLab's diff rules:new_linefor a line the merge request adds,old_linefor a line it removes, both for an unchanged context line. There is no REST equivalent of GitLab's Request changes state — to block a merge request, leave the findings as comments and do not approve. See the documentationWritev0.0.1 -
Get Issue
actionGets a single issue from repository. See the documentationRead-onlyv0.2.4
Triggers top 4 of 10
-
New Commit (Instant)
triggerEmit new event when a new commit is pushed to a branchInstantv0.1.4 -
New Branch (Instant)
triggerEmit new event when a new branch is createdInstantv0.1.3 -
New Project
triggerEmit new event when a project (i.e. repository) is createdv0.1.4 -
New Audit Event (Instant)
triggerEmit new event when a new audit event is createdInstantv0.1.4
TOOLS
Notion tools
The Notion tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 25
-
Append Block to Parent
actionAppend Markdown content to the bottom of a Notion page (or block). Thecontentis parsed from Markdown into Notion blocks — use it to add paragraphs, headings, bullet/numbered lists, to-dos, quotes, code, etc. Provide the page ID or URL (use Search to resolve a page name into an ID). To change a database row's property values instead, use Update Page. See the documentationWritev1.0.1 -
Complete File Upload
actionUse this action to finalize amode=multi_partfile upload after all of the parts have been sent successfully. See the documentationWritev0.0.11 -
Copy Page From Template
actionCopy an EXISTING page (template) into a new page with a new title. Use this ONLY when the user is reusing the structure of an existing page as a template (e.g. "copy this offer letter template for a new candidate"). Do NOT use to create a new page with original content — for that, use Create Page. The source page must already exist in Notion and is identified by its page ID. See the documentationWritev0.0.26 -
Create Comment
actionAdd a comment to a Notion page, or reply to an existing discussion thread. Provide either a page ID/URL (use Search to resolve a page name) or a discussion ID — not both. See the documentationWritev0.1.1 -
Create Database
actionCreate a new Notion database (data source) as a subpage of a parent page, defining its column schema. Provide the parent page ID or URL (use Search to resolve a page name into an ID).propertiesis a JSON object of column-name → column type. Each value is a property schema object, or shorthand for simple types:{ "Name": "title", "Quantity": "number", "Category": { "select": { "options": [ { "name": "A" }, { "name": "B" } ] } } }. Exactly one column must be thetitletype. See the documentationWritev1.0.1 -
Create File Upload
actionCreate a file upload. See the documentationWritev0.0.11 -
Create Page
actionCreate a new Notion page. Theparentcan be either another page (creates a subpage) or a database/data source (creates a row in that database). Provide the parent's ID or URL — use Search to resolve a name into an ID. When the parent is a database, setpropertiesto a flat JSON object of column-name → value (e.g.{ "Status": "Active", "ThreatLevel": 9 }); call Retrieve Database Schema first to learn the exact column names and valid select options.contentis the page body as Markdown (headings, bullet lists, paragraphs, etc.). See the documentationWritev1.0.1 -
Create Page from Data Source
actionCreate a page from a data source. See the documentationWritev2.0.3
Triggers top 4 of 9
-
New Comment Created
triggerEmit new event when a new comment is created in a page or block. See the documentationv0.0.9 -
New Data Source Created
triggerEmit new event when a data source is created. See the documentationv0.1.1 -
New or Updated Page in Data Source (By Property)
triggerEmit new event when a page is created or updated in the selected data source. See the documentationv1.0.1 -
New or Updated Page in Data Source (By Timestamp)
triggerEmit new event when a page is created or updated in the selected data source. See the documentationv1.0.1
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
- gitlab,notion
- Primary app
- GitLab (gitlab)
- Second app
- Notion (notion)
- Authentication
- OAuth + OAuth
- Available actions
- 53
- Available triggers
- 19