Pipedrive logo

Get Pipeline Details (Pipedrive)

Pipedrive → Get Pipeline Details (Pipedrive)

POST/v1/pipedrive-get-pipeline-details
texau__pipedrive-get-pipeline-detailscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/pipedrive-get-pipeline-details
{
  "id": 1
}
200 Accepted
{
  "ok": true,
  "data": {
    "success": true,
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "order_nr": 1,
    "is_deleted": true,
    "is_deal_probability_enabled": true,
    "add_time": "sample",
    "update_time": "sample"
  }
}

Retrieve the details of a specific pipeline by its ID from Pipedrive using API v2.

Install

Add get pipeline 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-pipeline-details

When to use this.

The "Get Pipeline Details" action for Pipedrive allows users to retrieve comprehensive information about a specific sales pipeline by its unique ID using API v2. This action requires a single input parameter, the pipeline ID (number), which identifies the pipeline to be fetched. Upon execution, it returns a set of output fields including success status (boolean), pipeline ID (id), pipeline name (text), order number (number), deletion status (boolean), deal probability status (boolean), and timestamps for when the pipeline was added and last updated (date). This functionality is essential for CRM applications, enabling sales teams to access and manage pipeline data effectively, track sales processes, and analyze performance metrics. Use cases include monitoring pipeline status, integrating with reporting tools, and enhancing sales strategy by understanding pipeline configurations.

Try it

Run a sample request.

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

Get Pipeline Details (Pipedrive)

Try it

The ID of the pipeline 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
  • success
    Success
    nullableboolean
  • id
    Id
    number
  • unique_name
    Unique Name
    text
  • order_nr
    Order Nr
    nullablenumber
  • is_deleted
    Is Deleted
    nullableboolean
  • is_deal_probability_enabled
    Is Deal Probability Enabled
    boolean
  • add_time
    Add Time
    nullabletext
  • update_time
    Update Time
    nullabletext

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/pipedrive-get-pipeline-details
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-get-pipeline-details' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"id":1}'
200 Accepted
{
  "ok": true,
  "data": {
    "success": true,
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "order_nr": 1,
    "is_deleted": true,
    "is_deal_probability_enabled": true,
    "add_time": "sample",
    "update_time": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get Pipeline 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 pipeline 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 Pipeline 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 Pipeline Details (Pipedrive) in 60 seconds.

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

Start free →Read the API docs