Hunter ACTION
Create Lead
Create a new lead in your Hunter account. See the documentation.
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Hunter account once, then configure and run Create 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: "hunter-create-lead",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
hunter: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
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": "hunter-create-lead",
"configured_props": {
"hunter": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email",
"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": "hunter",
},
},
},
)
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: "hunter-create-lead",
arguments: {
email: "Email",
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 |
|---|---|---|
email Email | string | The email address of the lead. Required |
firstName First Name | string | The first name of the lead. Optional |
lastName Last Name | string | The last name of the lead. Optional |
position Position | string | The job title of the lead. Optional |
company Company | string | The name of the company the lead is working in. Optional |
companyIndustry Company Industry | string | The sector of the company. Optional |
companySize Company Size | string | The size of the company the lead is working in. Optional |
confidenceScore Confidence Score | integer | Estimation of the probability the email address returned is correct, between 0 and 100. Optional |
website Website | string | The domain name of the company. Optional |
countryCode Country Code | string | The country of the lead (ISO 3166-1 alpha-2 standard). Optional |
linkedinUrl LinkedIn URL | string | The address of the public profile on LinkedIn. Optional |
phoneNumber Phone Number | string | The phone number of the lead. Optional |
twitter Twitter | string | The Twitter handle of the lead. Optional |
notes Notes | string | Some personal notes about the lead. Optional |
source Source | string | The source where the lead has been found. Optional |
leadsListId Leads List ID | string | The identifier of the list the lead belongs to. If not specified, the lead is saved in the last list created. Optional Dynamic |
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
- hunter-create-lead
- Version
- 0.0.2
- App
- Hunter
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗