Pipedrive ACTION
List Projects
Lists projects in your Pipedrive account. Use the returned IDs with Get Project, Update Project, Delete Project, or Create Task. See the documentation
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Pipedrive account once, then configure and run List Projects 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: "pipedrive-list-projects",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pipedrive: { authProvisionId: "apn_xxxxxxx" },
status: "Status",
phaseId: "Phase 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": "pipedrive-list-projects",
"configured_props": {
"pipedrive": { "authProvisionId": "apn_xxxxxxx" },
"status": "Status",
"phaseId": "Phase 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": "pipedrive",
},
},
},
)
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: "pipedrive-list-projects",
arguments: {
status: "Status",
phaseId: "Phase 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 |
|---|---|---|
status Status | string | Filter by project status. One of: open, completed, canceled, deleted (deleted excluded by default). Optional |
phaseId Phase ID | string | Filter by phase ID. Run List Project Phases first to obtain a valid phase ID. Optional |
dealId Deal ID | string | Filter by associated deal ID. Optional |
personId Person ID | string | Filter by associated person ID. Use List Persons to obtain a valid person ID. Optional |
orgId Organization ID | string | Filter by associated organization ID. Use List Organizations to obtain a valid organization ID. Optional |
filterId Filter ID | integer | The ID of the filter to apply to projects. Use List Filters to obtain a valid filter ID. Optional |
limit Limit | integer | For pagination, the number of entries to return. Min 1, max 500 (server-side cap). Defaults to 100 if omitted. Optional |
cursor Cursor | string | For pagination, the cursor to the next page of results (from additional_data.next_cursor). If omitted, the first page is 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
- pipedrive-list-projects
- Version
- 0.0.2
- App
- Pipedrive
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗