IMPLEMENTATION
Call this tool
Connect a user's GitLab account once, then configure and run Create Epic from your backend or agent.
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 result = await pd.actions.run({
id: "gitlab-create-epic",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
gitlab: { authProvisionId: "apn_xxxxxxx" },
groupId: "Group ID",
parent_id: "Parent ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "gitlab-create-epic",
"configured_props": {
"gitlab": { "authProvisionId": "apn_xxxxxxx" },
"groupId": "Group ID",
"parent_id": "Parent ID"
}
}'// 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",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "gitlab-create-epic",
arguments: {
groupId: "Group ID",
parent_id: "Parent ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
groupId Group ID | string | Select a Group or use a custom Group ID. You must be an Owner of this group Required Dynamic |
parent_id Parent ID | string | The internal ID of a project's epic. This feature is restricted to Gitlab's Premium and Ultimate tiers. Optional Dynamic |
title Title | string | The title of the epic Required |
labels Labels | string[] | The comma-separated list of labels Optional Dynamic |
description Description | string | The description of the issue Optional |
color Color | string | The color of the epic. Introduced in GitLab 14.8, behind a feature flag named epic_highlight_color (disabled by default) Optional |
confidential Confidential | boolean | Whether the epic should be confidential Optional |
created_at Created at | string | When the epic was created. Date time string, ISO 8601 formatted, for example 2016-03-11T03:45:40Z . Requires administrator or project/group owner privileges (available in GitLab 13.5 and later) Optional |
start_date_is_fixed Start Date Is Fixed | boolean | Whether start date should be sourced from start_date_fixed or from milestones (in GitLab 11.3 and later) Optional |
due_date_is_fixed Due Date Is Fixed | boolean | Whether due date should be sourced from due_date_fixed or from milestones (in GitLab 11.3 and later) Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- gitlab-create-epic
- Version
- 0.0.6
- App
- GitLab
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗