View as Markdown
Jira icon

Jira ACTION

List Epics

Returns all epics from a board, for the given board ID. See the documentation
  • Action
  • Read only
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Jira account once, then configure and run List Epics 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-list-epics",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    boardId: "Board ID",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

List Epics inputs
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
boardId Board ID string
The ID of the board
Required Dynamic
startAt Start At integer
The starting index of the returned epics. Base index: 0.
Optional
maxResults Max Results integer
The maximum number of epics to return.
Optional
done Done boolean
Filters results to epics that are either done or not done. If not provided, all epics are returned.
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
jira-list-epics
Version
0.0.8
App
Jira
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes