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.

Get All Leads (Pipedrive)

Pipedrive → Get All Leads (Pipedrive)

POST/v1/pipedrive-get-all-leads

texau__pipedrive-get-all-leadscrm

Run in Studio →Open in MCP

cURL · api.texau.app

84ms

POST/v1/pipedrive-get-all-leads

{
  "limit": 1,
  "sort_by": "sample-value"
}

200 Accepted

{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "title": "sample",
    "owner_id": "rec_4f3a91",
    "creator_id": "rec_4f3a91",
    "label_id": "rec_4f3a91",
    "person_id": "rec_4f3a91",
    "organization_id": "rec_4f3a91",
    "source_name": "sample",
    "origin": "sample",
    "channel": 1,
    "channel_id": "rec_4f3a91",
    "is_archived": true,
    "was_seen": true,
    "value_amount": 1,
    "value_currency": "sample",
    "expected_close_date": "sample",
    "next_activity_id": "rec_4f3a91",
    "add_time": "sample",
    "update_time": "sample",
    "visible_to": "sample",
    "cc_email": "[email protected]"
  }
}

Retrieves all unarchived leads from Pipedrive

Install

Add get all 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-get-all-leads

When to use this.

The "Get All Leads (Pipedrive)" action retrieves all unarchived leads from the Pipedrive CRM, providing users with a comprehensive overview of their lead data sorted by creation time from oldest to newest. Users can customize their query with optional input parameters such as "limit," which specifies the number of leads to return per page (defaulting to 100), and "sort_by," allowing for sorting based on specific fields. The output includes essential lead information, including IDs, titles, ownership details, source names, and financial metrics, with data types ranging from IDs and text to numbers, booleans, and dates. This action is particularly useful for sales teams and marketers seeking to analyze lead performance, track engagement, and manage sales pipelines effectively within the CRM category.

Try it

Run a sample request.

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

Get All Leads (Pipedrive)

Try it

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
nullablenumber
creator_id
Creator Id
nullablenumber
label_id
Label Id
nullablearray
person_id
Person Id
number
organization_id
Organization Id
number
source_name
Source Name
nullabletext
origin
Origin
nullabletext
channel
Channel
nullablenumber
channel_id
Channel Id
nullabletext
is_archived
Is Archived
nullableboolean
was_seen
Was Seen
nullableboolean
value_amount
Value Amount
number
value_currency
Value Currency
text
expected_close_date
Expected Close Date
nullabletext
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-all-leads. Auth: x-api-key.

cURL · api.texau.app

84ms

POST/v1/pipedrive-get-all-leads

curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-get-all-leads' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"limit":1,"sort_by":"sample-value"}'

200 Accepted

{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "title": "sample",
    "owner_id": "rec_4f3a91",
    "creator_id": "rec_4f3a91",
    "label_id": "rec_4f3a91",
    "person_id": "rec_4f3a91",
    "organization_id": "rec_4f3a91",
    "source_name": "sample",
    "origin": "sample",
    "channel": 1,
    "channel_id": "rec_4f3a91",
    "is_archived": true,
    "was_seen": true,
    "value_amount": 1,
    "value_currency": "sample",
    "expected_close_date": "sample",
    "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 All 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.

Input	Status	Score
[email protected]	valid	96
[email protected]	risky	54
[email protected]	invalid	12

Workflow

A real example.

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

Step 1TriggerNew row, webhook, or schedule.

Step 2Get All 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.

Code	Cause	Fix
200 OK	Action ran. Data in `data`.	Read response.
400 Bad Request	Missing or malformed input.	Validate against the input schema.
401 Unauthorized	Missing or invalid `x-api-key`.	Re-issue from /api-platform.
403 Forbidden	Workspace lacks plan tier.	Upgrade or contact sales.
404 Not Found	Action key not recognized.	Verify the slug.
429 Rate Limited	Per-minute or per-day cap hit.	Backoff; reduce concurrency.
500 Server Error	Unexpected TexAu issue.	Retry with backoff.
502 Bad Gateway	Upstream provider 5xx.	Retry; we surface root cause.
504 Timeout	Upstream 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 All Leads (Pipedrive) in 60 seconds.

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

Start free →Read the API docs

Get All Leads (Pipedrive)

Add get all leads (pipedrive) to your MCP client.

When to use this.

Run a sample request.

Get All Leads (Pipedrive)

Output schema.

Copy-pasteable snippets.

How this fits a workflow.

Get Deals by Person (Pipedrive)

Delete Lead (Pipedrive)

Search Deals (Pipedrive)

Results land in a TexAu table.

A real example.

Who runs this.

Rate limits & reliability.

HTTP status codes.

What it costs to run.

More Pipedrive actions.

Get Deals by Person (Pipedrive)

Delete Lead (Pipedrive)

Search Deals (Pipedrive)

Search Organizations (Pipedrive)

FAQ.

Is this real-time?

Do I get charged on failure?

Does it work with Claude / Cursor via MCP?

What CRMs can I push results to?

Run Get All Leads (Pipedrive) in 60 seconds.