Close ACTION
Update Lead
Updates a lead. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Close 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: "close-update-lead",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
close: { authProvisionId: "apn_xxxxxxx" },
lead: "Lead ID",
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": "close-update-lead",
"configured_props": {
"close": { "authProvisionId": "apn_xxxxxxx" },
"lead": "Lead ID",
"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": "close",
},
},
},
)
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: "close-update-lead",
arguments: {
lead: "Lead ID",
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 |
|---|---|---|
lead Lead ID | string | Lead to be selected Required Dynamic |
name Name | string | Name of the lead Optional |
url Url | string | Url Optional |
description Description | string | Description of the lead Optional |
statusId Status ID | string | Lead Statuses represent a Lead's current relationship to your company. See the docs Optional Dynamic |
contacts Contacts | string[] | Please provide an object structure for each row. e.g.:,
{
"name": "Gob",
"title": "Sr. Vice President",
"emails": [ { "type": "office", "email": "gob@example.com" } ],
"phones": [ { "type": "office", "phone": "8004445555" } ]
} Optional |
addresses Addresses | string[] | Please provide an object structure for each row. e.g.:,
{
"label": "business",
"address_1": "747 Howard St",
"address_2": "Room 3",
"city": "San Francisco",
"state": "CA",
"zipcode": "94103",
"country":"US",
} Optional |
moreFields More Fields | object | Additional properties not listed as props 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
- close-update-lead
- Version
- 0.1.3
- App
- Close
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗