Pipedrive logo

Search Leads (Pipedrive)

Pipedrive → Search Leads (Pipedrive)

POST/v1/pipedrive-search-leads
texau__pipedrive-search-leadscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/pipedrive-search-leads
{
  "term": "sample-value",
  "field": "sample-value",
  "exact_match": true,
  "person_id": 1,
  "organization_id": "Acme, Inc.",
  "limit": 1
}
200 Accepted
{
  "ok": true,
  "data": {
    "result_score": 92,
    "id": "rec_4f3a91",
    "title": "sample",
    "type": "sample",
    "owner_id": "rec_4f3a91",
    "person_id": "rec_4f3a91",
    "person_name": "sample",
    "organization_id": "rec_4f3a91",
    "organization_name": "sample",
    "value_amount": 1,
    "value_currency": "sample",
    "is_archived": true,
    "visible_to": 1,
    "mobile_number": "sample",
    "email": "[email protected]",
    "custom_fields": "sample",
    "note": "sample"
  }
}

Searches all leads by title, notes, and/or custom fields using the Pipedrive API v2.

Install

Add search leads (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-search-leads

When to use this.

The "Search Leads (Pipedrive)" action enables users to efficiently search for leads within the Pipedrive CRM by utilizing various criteria such as title, notes, and custom fields through the Pipedrive API v2. Key input parameters include 'term', which specifies the search term (minimum of 2 characters), 'fields' for defining specific search areas, and 'exact_match' to filter results for full matches. Additional filters like 'person_id' and 'organization_id' allow for targeted searches based on associated individuals or organizations, while 'limit' controls the number of results returned per page. The output includes essential data points such as lead ID, title, owner ID, person and organization details, value amounts, and notes, all categorized under semantic types like id, text, number, boolean, and email. This action is particularly useful for sales teams and CRM users looking to streamline lead management, enhance customer engagement, and improve sales strategies by quickly locating relevant leads based on specific criteria.

Try it

Run a sample request.

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

Search Leads (Pipedrive)

Try it

The search term to look for. Minimum 2 characters (or 1 if exact match).

Comma-separated list of fields to search within. Defaults to all.

If enabled, only full exact matches against the given term are returned.

Filter leads by the provided Person ID

Filter leads by the provided Organization ID

Items per page

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • result_score
    Result Score
    nullablenumber
  • id
    Id
    text
  • title
    Title
    text
  • type
    Type
    nullabletext
  • owner_id
    Owner Id
    nullablenumber
  • person_id
    Person Id
    number
  • person_name
    Person Name
    text
  • organization_id
    Organization Id
    number
  • organization_name
    Organization Name
    text
  • value_amount
    Value Amount
    number
  • value_currency
    Value Currency
    text
  • is_archived
    Is Archived
    nullableboolean
  • visible_to
    Visible To
    nullablenumber
  • mobile_number
    Mobile Number
    nullabletext
  • email
    Email
    nullabletext
  • custom_fields
    Custom Fields
    nullabletext
  • note
    Note
    nullabletext

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/pipedrive-search-leads
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-search-leads' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"term":"sample-value","field":"sample-value","exact_match":true,"person_id":1,"organization_id":"Acme, Inc.","limit":1}'
200 Accepted
{
  "ok": true,
  "data": {
    "result_score": 92,
    "id": "rec_4f3a91",
    "title": "sample",
    "type": "sample",
    "owner_id": "rec_4f3a91",
    "person_id": "rec_4f3a91",
    "person_name": "sample",
    "organization_id": "rec_4f3a91",
    "organization_name": "sample",
    "value_amount": 1,
    "value_currency": "sample",
    "is_archived": true,
    "visible_to": 1,
    "mobile_number": "sample",
    "email": "[email protected]",
    "custom_fields": "sample",
    "note": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Search Leads (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 Search Leads (Pipedrive) in 60 seconds.

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

Start free →Read the API docs