Pipedrive ACTION
Update Person
Updates an existing person 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 Person 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-person",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pipedrive: { authProvisionId: "apn_xxxxxxx" },
personId: 10,
name: "Name",
},
})
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-person",
"configured_props": {
"pipedrive": { "authProvisionId": "apn_xxxxxxx" },
"personId": 10,
"name": "Name"
}
}'// 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-person",
arguments: {
personId: 10,
name: "Name",
},
})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 |
|---|---|---|
personId Person ID | integer | The ID of the person to update Required Dynamic |
name Name | string | New name of the person Optional |
ownerId Owner ID | integer | ID of the user who will be marked as the owner of this person. When omitted, the authorized user ID will be used. Optional Dynamic |
organizationId Organization ID | integer | ID of the organization this person will belong to Optional Dynamic |
emails Emails | string[] | Email addresses (one or more) associated with the person, presented in the same manner as received by GET request of a person. Example: {"value":"email1@email.com", "primary":true, "label":"work"} Optional |
phones Phones | string[] | Phone numbers (one or more) associated with the person, presented in the same manner as received by GET request of a person. Example: {"value":"12345", "primary":true, "label":"work"} Optional |
visibleTo Visible To | integer | Visibility of the person. If omitted, visibility will be set to the default visibility setting of this item type for the authorized user. 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-person
- Version
- 0.0.17
- App
- Pipedrive
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗