Pipedrive ACTION
Add Labels
Adds labels to a lead, person, deal, or organization in Pipedrive. See the documentation
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Pipedrive account once, then configure and run Add Labels 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-add-labels",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pipedrive: { authProvisionId: "apn_xxxxxxx" },
type: "Type",
leadId: "Lead 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-add-labels",
"configured_props": {
"pipedrive": { "authProvisionId": "apn_xxxxxxx" },
"type": "Type",
"leadId": "Lead 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-add-labels",
arguments: {
type: "Type",
leadId: "Lead 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 |
|---|---|---|
type Type | string | The type of the item to add labels to Required |
leadId Lead ID | string | The ID of the lead to add labels to Optional Dynamic |
personId Person ID | integer | The ID of the person to add labels to Optional Dynamic |
dealId Deal ID | string | The ID of the deal to add labels to Optional Dynamic |
organizationId Organization ID | integer | The ID of the organization to add labels to Optional Dynamic |
leadLabelIds Lead Label IDs | string[] | The IDs of the lead labels to associate with the lead Optional Dynamic |
personLabelIds Person Label IDs | integer[] | The IDs of the person labels to associate with the person Optional Dynamic |
dealLabelIds Label IDs | integer[] | The IDs of labels assigned to the deal Optional Dynamic |
organizationLabelIds Organization Label IDs | integer[] | The IDs of the organization labels to associate with the organization Optional Dynamic |
replaceExistingLabels Replace Existing Labels | boolean | Set to true to replace the existing labels with the new ones, false to add the new labels to the existing ones. Defaults to false. 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-add-labels
- Version
- 0.0.5
- App
- Pipedrive
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗