Asana ACTION
List Portfolio Items
Returns a list of the items (projects) in the given portfolio. Use this after List Portfolios to answer count, timing, and spend questions; the default Opt Fields include
created_at, start_on, due_on, and custom_fields. Archived filtering happens client-side because Asana has no server-side filter on this endpoint. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Asana account once, then configure and run List Portfolio Items 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: "asana-list-portfolio-items",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
asana: { authProvisionId: "apn_xxxxxxx" },
portfolioId: "Portfolio",
optFields: ["Opt Fields"],
},
})
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": "asana-list-portfolio-items",
"configured_props": {
"asana": { "authProvisionId": "apn_xxxxxxx" },
"portfolioId": "Portfolio",
"optFields": ["Opt Fields"]
}
}'// 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": "asana",
},
},
},
)
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: "asana-list-portfolio-items",
arguments: {
portfolioId: "Portfolio",
optFields: ["Opt Fields"],
},
})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 |
|---|---|---|
portfolioId Portfolio | string | The portfolio GID. Use the List Portfolios action to find available portfolio GIDs. Required |
optFields Opt Fields | string[] | Optional item properties to include in the response (defaults to name, archived, created_at, start_on, due_on, owner, resource_type, custom_fields). Nested paths are allowed; gid is always returned. See the documentation Optional |
excludeArchived Exclude Archived | boolean | Filter out archived projects from the results. The filter is applied client-side because Asana has no server-side archived filter on this endpoint. Optional |
maxResults Max Results | integer | The maximum total number of results to return across all paginated API calls. Each page fetches up to 100 items (Asana's maximum); this cap is applied after auto-pagination completes. 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
- asana-list-portfolio-items
- Version
- 0.0.2
- App
- Asana
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗