Pipedrive ACTION
Update Lead
Updates a lead 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 Update Lead 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-update-lead",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pipedrive: { authProvisionId: "apn_xxxxxxx" },
leadId: "Lead ID",
title: "Title",
},
})
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-update-lead",
"configured_props": {
"pipedrive": { "authProvisionId": "apn_xxxxxxx" },
"leadId": "Lead ID",
"title": "Title"
}
}'// 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-update-lead",
arguments: {
leadId: "Lead ID",
title: "Title",
},
})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 |
|---|---|---|
leadId Lead ID | string | ID of the lead this activity will be associated with Required Dynamic |
title Title | string | Title of the lead Optional |
personId Person ID | integer | The ID of the person this lead will be linked to. If the person does not exist yet, it needs to be created first. Optional Dynamic |
organizationId Organization ID | integer | ID of the organization this lead will belong to Optional Dynamic |
ownerId Owner ID | integer | ID of the user who will be marked as the owner of this lead Optional Dynamic |
labelIds Lead Label IDs | string[] | The IDs of the lead labels to associate with the lead Optional Dynamic |
value Value | object | Potential value of the lead, e.g. { "amount": 200, "currency": "EUR" } Optional |
expectedCloseDate Expected Close Date | string | The date of when the deal which will be created from the lead is expected to be closed. In ISO 8601 format: YYYY-MM-DD. Optional |
visibleTo Visible To | string | The visibility of the lead. If omitted, the visibility will be set to the default visibility setting of this item type for the authorized user. Read more about visibility groups here. Optional |
wasSeen Was Seen | boolean | A flag indicating whether the lead was seen by someone in the Pipedrive UI Optional |
isArchived Is Archived | boolean | A flag indicating whether the lead is archived or not 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-update-lead
- Version
- 0.0.7
- App
- Pipedrive
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗