MULTI-APP TOOLKIT
Build with GitLab + Slack
- Multi-app
- One MCP session
- 78 actions
- 19 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every GitLab and Slack 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,slack_v2",
},
},
},
)
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 Slack 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, slackV2Tools] =
await Promise.all([
pd.components.list({ app: "gitlab" }),
pd.components.list({ app: "slack_v2" }),
])
// 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=slack_v2" \
-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
Slack
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
Slack tools
The Slack tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 50
-
Send Message to Channel
actionSend a message to a public or private channel. Legacy, channel-only variant — prefer Post Message for new integrations: it covers channels, users, and groups from a single tool, and also supports threaded replies and unfurl settings. Use this tool only if a workflow specifically needs to target a channel exclusively, without the user/group support Post Message offers. See the documentationWritev0.2.4 -
Add Emoji Reaction
actionAdd an emoji reaction to a message. See the documentationWritev0.0.28 -
Add Reaction
actionAdd an emoji reaction to a message. Accepts a channel ID (preferred — resolves instantly) or channel name (resolved by scanning up to 5 pages, ~5,000 channels, of the workspace's channel list — a name beyond that bound will not be found). Use Get Channel History or Search to find the message timestamp. Emoji name should be without colons (e.g.thumbsup,fire,heart). See the documentationWritev0.0.8 -
Archive Channel
actionArchive a public or private channel. Direct messages and group DMs can't be archived — pass a channel ID (e.g.C1234567890), not a user or group ID. See the documentationWritev0.0.36 -
Browse Files
actionList files shared in a channel or across the workspace. Accepts a channel ID (preferred — resolves instantly) or channel name (resolved by scanning up to 5 pages, ~5,000 channels, of the workspace's channel list — a name beyond that bound will not be found). Filter by file type (e.g.images,pdfs,snippets). Returns file metadata including name, type, size, and download URL. See the documentationRead-onlyv0.0.8 -
Build and Send a Block Kit Message
actionConfigure custom blocks and send to a channel, group, or user. See the documentation.Writev0.5.11 -
Create a Channel
actionCreate a new channel. See the documentationWritev0.0.36 -
Create Reminder
actionCreate a reminder. See the documentationWritev0.0.37
Triggers top 4 of 9
-
New Channel Created (Instant)
triggerEmit new event when a new channel is created.Instantv0.0.20 -
New Interaction Events (Instant)
triggerEmit new events on new Slack interactivity events sourced from Block Kit interactive elements, Slash commands, or Shortcuts.Instantv0.0.31 -
New Keyword Mention (Instant)
triggerEmit new event when a specific keyword is mentioned in a channelInstantv0.1.10 -
New Message In Channels (Instant)
triggerEmit new event when a new message is posted to one or more channelsInstantv1.1.10
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,slack_v2
- Primary app
- GitLab (gitlab)
- Second app
- Slack (slack_v2)
- Authentication
- OAuth + OAuth
- Available actions
- 78
- Available triggers
- 19