Pipedrive ACTION
Update Deal
Updates the properties of a deal. See the Pipedrive API docs for Deals here
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Pipedrive account once, then configure and run Update Deal 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-deal",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
pipedrive: { authProvisionId: "apn_xxxxxxx" },
dealId: "Deal 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-deal",
"configured_props": {
"pipedrive": { "authProvisionId": "apn_xxxxxxx" },
"dealId": "Deal 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-deal",
arguments: {
dealId: "Deal 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 |
|---|---|---|
dealId Deal ID | string | ID of the deal Required Dynamic |
title Title | string | Deal title Optional |
ownerId User ID | integer | ID of the user who will be marked as the owner of this deal. If omitted, the authorized user ID will be used. Optional Dynamic |
personId Person ID | integer | ID of the person this deal will be associated with Optional Dynamic |
orgId Organization ID | integer | ID of the organization this deal will be associated with Optional Dynamic |
pipelineId Pipeline ID | integer | ID of the pipeline this activity will be associated with Optional Dynamic |
stageId Stage ID | integer | ID of the stage this deal will be placed in a pipeline (note that you can't supply the ID of the pipeline as this will be assigned automatically based on stage_id). If omitted, the deal will be placed in the first stage of the default pipeline. Get the stage_id from here. Optional Dynamic |
value Value | string | Value of the deal. If omitted, value will be set to 0. Optional |
currency Currency | string | Currency of the deal. Accepts a 3-character currency code. If omitted, currency will be set to the default currency of the authorized user. Optional |
status Status | string | open = Open, won = Won, lost = Lost, deleted = Deleted. If omitted, status will be set to open. Optional |
probability Probability | integer | Deal success probability percentage. Used/shown only when deal_probability for the pipeline of the deal is enabled. Optional |
lostReason Lost Reason | string | Optional message about why the deal was lost (to be used when status=lost) Optional |
visibleTo Visible To | integer | Visibility of the deal. If omitted, visibility will be set to the default visibility setting of this item type for the authorized user. Optional |
note Note | string | A note to add to the deal 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-deal
- Version
- 0.1.24
- App
- Pipedrive
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗