Pipedrive logo

Get Person (Pipedrive)

PipedriveGet Person (Pipedrive)

POST/v1/pipedrive-get-person
texau__pipedrive-get-personcrm
cURL · api.texau.app
84ms
POST/v1/pipedrive-get-person
{
  "person_id": 1
}
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "first_name": "sample",
    "last_name": "sample",
    "owner_id": "rec_4f3a91",
    "org_id": "rec_4f3a91",
    "is_deleted": true,
    "visible_to": 1,
    "add_time": "sample",
    "update_time": "sample",
    "next_activity_id": "rec_4f3a91",
    "last_activity_id": "rec_4f3a91",
    "open_deal_count": 1,
    "related_open_deal_count": 1,
    "closed_deal_count": 1,
    "related_closed_deal_count": 1,
    "won_deal_count": 1,
    "related_won_deal_count": 1,
    "lost_deal_count": 1,
    "related_lost_deal_count": 1,
    "participant_open_deal_count": 1,
    "participant_closed_deal_count": 1,
    "email_message_count": "[email protected]",
    "activity_count": 1,
    "done_activity_count": 1,
    "undone_activity_count": 1,
    "file_count": 1,
    "note_count": 1,
    "follower_count": 1,
    "last_incoming_mail_time": "sample",
    "last_outgoing_mail_time": "sample",
    "primary_email": "[email protected]",
    "primary_mobile_number": "sample",
    "smart_bcc_email": "[email protected]",
    "label_id": "rec_4f3a91"
  }
}

Retrieves the details of a specific person from Pipedrive using their unique ID, including deal counts, activity counts, and email tracking.

Install

Add get person (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-person

When to use this.

The "Get Person (Pipedrive)" action is designed to retrieve detailed information about a specific individual in the Pipedrive CRM system using their unique person ID. By providing the personId as an input parameter, users can access a wealth of data including the person's full name, email, phone number, and various metrics related to deals and activities, such as open and closed deal counts, activity counts, and email tracking details. The output fields encompass essential semantic types like fullName, email, and phone, along with identifiers for organization and ownership. This action is particularly useful for sales teams and customer relationship managers who need to track interactions, manage leads, and analyze performance metrics related to individual contacts, making it an invaluable tool within the CRM category.

Try it

Run a sample request.

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

Get Person (Pipedrive)

Try it

The ID of the person to be retrieved.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • id
    Id
    number
  • unique_name
    Unique Name
    text
  • first_name
    First Name
    text
  • last_name
    Last Name
    text
  • owner_id
    Owner Id
    number
  • org_id
    Org Id
    number
  • is_deleted
    Is Deleted
    nullableboolean
  • visible_to
    Visible To
    nullablenumber
  • add_time
    Add Time
    nullabletext
  • update_time
    Update Time
    nullabletext
  • next_activity_id
    Next Activity Id
    nullablenumber
  • last_activity_id
    Last Activity Id
    nullablenumber
  • open_deal_count
    Open Deal Count
    nullablenumber
  • related_open_deal_count
    Related Open Deal Count
    nullablenumber
  • closed_deal_count
    Closed Deal Count
    nullablenumber
  • related_closed_deal_count
    Related Closed Deal Count
    nullablenumber
  • won_deal_count
    Won Deal Count
    nullablenumber
  • related_won_deal_count
    Related Won Deal Count
    nullablenumber
  • lost_deal_count
    Lost Deal Count
    nullablenumber
  • related_lost_deal_count
    Related Lost Deal Count
    nullablenumber
  • participant_open_deal_count
    Participant Open Deal Count
    nullablenumber
  • participant_closed_deal_count
    Participant Closed Deal Count
    nullablenumber
  • email_message_count
    Email Message Count
    nullablenumber
  • activity_count
    Activity Count
    nullablenumber
  • done_activity_count
    Done Activity Count
    nullablenumber
  • undone_activity_count
    Undone Activity Count
    nullablenumber
  • file_count
    File Count
    nullablenumber
  • note_count
    Note Count
    nullablenumber
  • follower_count
    Follower Count
    nullablenumber
  • last_incoming_mail_time
    Last Incoming Mail Time
    nullabletext
  • last_outgoing_mail_time
    Last Outgoing Mail Time
    nullabletext
  • primary_email
    Primary Email
    text
  • primary_mobile_number
    Primary Mobile Number
    text
  • smart_bcc_email
    Smart Bcc Email
    nullabletext
  • label_id
    Label Id
    nullablearray

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/pipedrive-get-person
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-get-person' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"person_id":1}'
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "first_name": "sample",
    "last_name": "sample",
    "owner_id": "rec_4f3a91",
    "org_id": "rec_4f3a91",
    "is_deleted": true,
    "visible_to": 1,
    "add_time": "sample",
    "update_time": "sample",
    "next_activity_id": "rec_4f3a91",
    "last_activity_id": "rec_4f3a91",
    "open_deal_count": 1,
    "related_open_deal_count": 1,
    "closed_deal_count": 1,
    "related_closed_deal_count": 1,
    "won_deal_count": 1,
    "related_won_deal_count": 1,
    "lost_deal_count": 1,
    "related_lost_deal_count": 1,
    "participant_open_deal_count": 1,
    "participant_closed_deal_count": 1,
    "email_message_count": "[email protected]",
    "activity_count": 1,
    "done_activity_count": 1,
    "undone_activity_count": 1,
    "file_count": 1,
    "note_count": 1,
    "follower_count": 1,
    "last_incoming_mail_time": "sample",
    "last_outgoing_mail_time": "sample",
    "primary_email": "[email protected]",
    "primary_mobile_number": "sample",
    "smart_bcc_email": "[email protected]",
    "label_id": "rec_4f3a91"
  }
}

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 person (pipedrive) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Person (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.

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 Person (Pipedrive) in 60 seconds.

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