Woodpecker.co ACTION
Create Or Update Prospect
This action creates/updates a prospect. See the docs here
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Woodpecker.co account once, then configure and run Create Or Update Prospect 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: "woodpecker_co-create-update-prospect",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
woodpecker_co: { authProvisionId: "apn_xxxxxxx" },
id: 10,
firstName: "First 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": "woodpecker_co-create-update-prospect",
"configured_props": {
"woodpecker_co": { "authProvisionId": "apn_xxxxxxx" },
"id": 10,
"firstName": "First 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": "woodpecker_co",
},
},
},
)
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: "woodpecker_co-create-update-prospect",
arguments: {
id: 10,
firstName: "First 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 |
|---|---|---|
id Id | integer | Prospect's ID. Optional Dynamic |
firstName First Name | string | Prospect's first name. Optional |
lastName Last Name | string | Prospect's last name. Optional |
email Email | string | Prospect's email address. Required |
company Company | string | Name of the company prospect is assigned to. Optional |
industry Industry | string | Type of industry prospect is working in. Optional |
website Website | string | Website address. Optional |
tags Tags | string | Prospect's tags. Optional |
title Job Title | string | Prospect's job title. Optional |
phone Phone | string | Prospect's phone number. Optional |
address Address | string | Prospect's address. Optional |
city City | string | Prospect's city. Optional |
state State | string | Prospect's state or another geographical region he's living in. Optional |
country Country | string | Prospect's country. Optional |
snippet Snippets | object | Any snippet provided for a prospect. Use snippet1, snippet2… snippet15 to sort prospects by chosen custom field. 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
- woodpecker_co-create-update-prospect
- Version
- 0.0.2
- App
- Woodpecker.co
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗