Jira ACTION
Download Attachment
Downloads a Jira issue attachment's binary content to the configured file-stash directory and returns its saved path plus the attachment's metadata (
filename, mimeType, size, etc.). Use this after locating an attachment via Get Issue (its fields.attachment[] array lists each attachment's id, filename, size, and mimeType), or from an attachment reference surfaced by another Jira action or trigger — pass that id as attachmentId. The file is saved in the file-stash directory as <attachmentId>-<sanitized filename> (the ID prefix avoids collisions when multiple attachments share the same filename); the returned filedata tuple points at that saved path for use in downstream file-input props. Jira's content endpoint responds with a redirect to a signed, short-lived media URL — this is followed automatically, so no extra configuration is required. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Jira account once, then configure and run Download Attachment 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: "jira-download-attachment",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jira: { authProvisionId: "apn_xxxxxxx" },
cloudId: "Cloud ID",
attachmentId: "Attachment 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": "jira-download-attachment",
"configured_props": {
"jira": { "authProvisionId": "apn_xxxxxxx" },
"cloudId": "Cloud ID",
"attachmentId": "Attachment 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": "jira",
},
},
},
)
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: "jira-download-attachment",
arguments: {
cloudId: "Cloud ID",
attachmentId: "Attachment 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 |
|---|---|---|
cloudId Cloud ID | string | The Jira Cloud site ID (for example, 11223344-a1b2-3b33-c444-def123456789). Use Get Cloud ID to discover IDs. See the documentation Required Dynamic |
attachmentId Attachment ID | string | The numeric ID of the attachment to download, e.g. 10001. This can be found in the id field of an attachment object, e.g. from an issue's fields.attachment[].id array (see the Get Issue action). Required |
syncDir SyncDir | dir | Required |
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
- jira-download-attachment
- Version
- 0.0.5
- App
- Jira
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗