MULTI-APP TOOLKIT
Build with GitLab + Gmail
- Multi-app
- One MCP session
- 49 actions
- 15 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitLab and Gmail 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,gmail",
},
},
},
)
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 Gmail 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, gmailTools] =
await Promise.all([
pd.components.list({ app: "gitlab" }),
pd.components.list({ app: "gmail" }),
])
// 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=gmail" \
-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
Gmail
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
Gmail tools
The Gmail tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 21
-
Add Label to Email
actionAdd label(s) to an email message. See the docsWritev0.0.16 -
Archive Email
actionArchive an email message. See the documentationWritev0.0.11 -
Bulk Archive Emails
actionArchive multiple emails at once. See the documentationWritev0.0.1 -
Create Draft
actionCreate an unsent draft in the authenticated Gmail account. Same parameter shape as Send Email — the difference is the message is saved to Drafts instead of being sent. For a reply-draft, passinReplyToMessageId(from Find Emails / Get Thread); the subject,References,In-Reply-To, andthreadIdare derived from the referenced message.bodyTypecontrols whetherbodyis treated as plain text (default) or HTML. To draft to yourself, pass"me"into— the action resolves it to the authenticated user's email address. No pre-call to Get Current User required. Attachments usefile-refinputs and require matchingattachmentFilenames[]entries. See the documentation.Writev0.2.3 -
Create Label
actionCreate a new user label in the authenticated Gmail mailbox and return its ID. Call this before Modify Labels whenever the label the user wants to apply doesn't yet exist — List Labels will tell you what's already there. Idempotent: if a label with the same name already exists, the action swallows the 409, looks it up by name, and returns the existing label withalreadyExisted: trueso the caller can proceed. Nested labels are expressed with/— e.g.Clients/Acmecreates or targets a sub-label underClients.coloris optional; when provided, bothtextColorandbackgroundColormust be supplied together and must come from Gmail's fixed palette. See the documentation.Writev0.1.3 -
Delete Email
actionMoves the specified message to the trash. See the documentationWritev0.0.5 -
Delete Label
actionImmediately and permanently delete a user-created label from the authenticated Gmail mailbox, removing it from every message and thread it was applied to. Only user-created labels can be deleted — Gmail's built-in system labels (INBOX,SENT,SPAM,TRASH, etc.) cannot. This deletes the label definition itself; to merely detach a label from specific messages without removing it, use Modify Labels withremoveLabelsinstead. See the documentation.Writev0.0.3 -
Download Attachment
actionDownload a Gmail message attachment to/tmpand return its path + metadata. File Stash syncs the file and exposes a presigned download URL so the caller can retrieve it. Call Find Emails (withformat: "full") or Get Thread first — attachment IDs only appear in full-format message reads; each returned message'spayload.parts[]enumerates attachments as{ body.attachmentId, filename, mimeType }. Pass the enclosing message'sidasmessageIdand the part'sbody.attachmentIdasattachmentId. Iffilenameis omitted, the action looks up the attachment's filename from the message payload. SetconvertToPdf: trueto convert image / HTML / plain-text / DOCX attachments to PDF during download; other MIME types are rejected. See the documentation.Read-onlyv0.1.3
Triggers top 4 of 5
-
New Attachment Received
triggerEmit new event for each attachment in a message received. This source is capped at 100 max new messages per run.v0.2.7 -
New Email Matching Search
triggerEmit new event when an email matching the search criteria is received. This source is capped at 100 max new messages per run.v0.1.7 -
New Email Received
triggerEmit new event when a new email is received.v0.3.7 -
New Labeled Email
triggerEmit new event when a new email is labeled.v0.1.7
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,gmail
- Primary app
- GitLab (gitlab)
- Second app
- Gmail (gmail)
- Authentication
- OAuth + OAuth
- Available actions
- 49
- Available triggers
- 15