Pipedrive logo

Get Lead Details (Pipedrive)

Pipedrive → Get Lead Details (Pipedrive)

POST/v1/pipedrive-get-lead-details
texau__pipedrive-get-lead-detailscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/pipedrive-get-lead-details
{
  "id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "title": "sample",
    "owner_id": "rec_4f3a91",
    "creator_id": "rec_4f3a91",
    "value_amount": 1,
    "value_currency": "sample",
    "expected_close_date": "sample",
    "person_id": "rec_4f3a91",
    "organization_id": "rec_4f3a91",
    "is_archived": true,
    "archive_time": "sample",
    "source_name": "sample",
    "origin": "sample",
    "origin_id": "rec_4f3a91",
    "channel": 1,
    "channel_id": "rec_4f3a91",
    "was_seen": true,
    "next_activity_id": "rec_4f3a91",
    "add_time": "sample",
    "update_time": "sample",
    "visible_to": "sample",
    "cc_email": "[email protected]"
  }
}

Retrieve the details of a specific lead by its ID (UUID) from Pipedrive using API v1.

Install

Add get lead details (pipedrive) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__pipedrive-get-lead-details

When to use this.

The "Get Lead Details (Pipedrive)" action allows users to retrieve comprehensive information about a specific lead within the Pipedrive CRM by providing the lead's unique identifier (UUID). The primary input parameter is the 'id' (text), which represents the UUID of the lead to be fetched. Upon execution, the action returns a variety of output fields, including the lead's ID, title, owner ID, value amount, expected close date, and various identifiers related to the person and organization associated with the lead. This action is essential for sales teams looking to access detailed lead information for effective follow-ups, reporting, and decision-making. It falls under the CRM category and supports various data types, including text, numbers, booleans, and emails, making it a versatile tool for managing customer relationships and sales pipelines.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Get Lead Details (Pipedrive)

Try it

The UUID of the lead you want to retrieve.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • id
    Id
    text
  • title
    Title
    text
  • owner_id
    Owner Id
    number
  • creator_id
    Creator Id
    nullablenumber
  • value_amount
    Value Amount
    number
  • value_currency
    Value Currency
    text
  • expected_close_date
    Expected Close Date
    text
  • person_id
    Person Id
    number
  • organization_id
    Organization Id
    number
  • is_archived
    Is Archived
    nullableboolean
  • archive_time
    Archive Time
    nullabletext
  • source_name
    Source Name
    nullabletext
  • origin
    Origin
    nullabletext
  • origin_id
    Origin Id
    nullabletext
  • channel
    Channel
    nullablenumber
  • channel_id
    Channel Id
    nullabletext
  • was_seen
    Was Seen
    nullableboolean
  • next_activity_id
    Next Activity Id
    nullablenumber
  • add_time
    Add Time
    nullabletext
  • update_time
    Update Time
    nullabletext
  • visible_to
    Visible To
    nullabletext
  • cc_email
    Cc Email
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/pipedrive-get-lead-details. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/pipedrive-get-lead-details
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-get-lead-details' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "title": "sample",
    "owner_id": "rec_4f3a91",
    "creator_id": "rec_4f3a91",
    "value_amount": 1,
    "value_currency": "sample",
    "expected_close_date": "sample",
    "person_id": "rec_4f3a91",
    "organization_id": "rec_4f3a91",
    "is_archived": true,
    "archive_time": "sample",
    "source_name": "sample",
    "origin": "sample",
    "origin_id": "rec_4f3a91",
    "channel": 1,
    "channel_id": "rec_4f3a91",
    "was_seen": true,
    "next_activity_id": "rec_4f3a91",
    "add_time": "sample",
    "update_time": "sample",
    "visible_to": "sample",
    "cc_email": "[email protected]"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get Lead Details (Pipedrive)→Get Deals by Person (Pipedrive)→Delete Lead (Pipedrive)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → get lead details (pipedrive) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Lead Details (Pipedrive)Pipedrive action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limitNo public cap
  • Per-day limitPlan-defined
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Pipedrive actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__pipedrive-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Get Lead Details (Pipedrive) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs