CONNECT APP
Build with Redmine
Productivity
- API key
MCP
Give your agent Redmine tools
Every Redmine action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Redmine account for each tool call — you store no tokens.
// 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": "redmine",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Issue:
const result = await mcp.callTool({
name: "redmine-create-issue",
arguments: {
projectId: 10,
trackerId: 10,
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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": "redmine",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Issue:
result = await session.call_tool("redmine-create-issue", {
"projectId": 10,
"trackerId": 10,
})API PROXY
Call the Redmine API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Redmine API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Redmine endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Redmine actions from your backend
Connect a user's Redmine account once, then run Create Issue on their behalf from your own code — TypeScript, Python, or plain HTTP.
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: "redmine-create-issue",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
redmine: { authProvisionId: "apn_xxxxxxx" },
projectId: 10,
trackerId: 10,
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="redmine-create-issue",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"redmine": {"authProvisionId": "apn_xxxxxxx"},
"projectId": 10,
"trackerId": 10,
},
)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": "redmine-create-issue",
"configured_props": {
"redmine": { "authProvisionId": "apn_xxxxxxx" },
"projectId": 10,
"trackerId": 10
}
}'TOOLS
Redmine actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Issue
actionCreates a new issue in Redmine. See the documentationWritev0.0.2 -
Delete User
actionDeletes a user from the Redmine platform. See the documentationWritev0.0.2 -
List Priority ID Options
actionRetrieves available options for the Priority ID field.Read-onlyv0.0.1 -
List Project ID Options
actionRetrieves available options for the Project ID field.Read-onlyv0.0.1 -
List Status ID Options
actionRetrieves available options for the Status ID field.Read-onlyv0.0.1 -
List Tracker ID Options
actionRetrieves available options for the Tracker ID field.Read-onlyv0.0.1 -
List User ID Options
actionRetrieves available options for the User ID field.Read-onlyv0.0.1 -
Update Project
actionUpdates an existing project in Redmine. See the documentationWritev0.0.2
EVENTS
Redmine triggers
Event sources your backend can deploy for users and receive through a webhook.
MULTI-APP
Use Redmine with other popular apps
Most products don't stop at one integration. Pair Redmine with the other apps your users rely on, and ship use cases that span both.
- App slug
- redmine
- Authentication
- API key
- Categories
- Productivity
- Actions
- 8
- Triggers
- 2
- API proxy
- Available