Pipedrive logo

Delete Lead (Pipedrive)

Pipedrive → Delete Lead (Pipedrive)

POST/v1/pipedrive-delete-lead
texau__pipedrive-delete-leadcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/pipedrive-delete-lead
{
  "id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "success": true
  }
}

Deletes a specific lead from Pipedrive using its ID.

Install

Add delete lead (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-delete-lead

When to use this.

The "Delete Lead (Pipedrive)" action allows users to efficiently remove a specific lead from their Pipedrive CRM system by utilizing the lead's unique identifier (UUID). This action requires a single input parameter, "id," which is the text-based UUID of the lead intended for deletion. Upon execution, the action returns a boolean output field named "success," indicating whether the lead was successfully deleted from the system. This functionality is essential for maintaining an organized CRM database, enabling users to eliminate outdated or irrelevant leads. Use cases for this action include lead management, data cleanup, and ensuring accurate sales tracking within the CRM category. By integrating this action, businesses can streamline their lead management processes and enhance overall operational efficiency.

Try it

Run a sample request.

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

Delete Lead (Pipedrive)

Try it

The UUID of the lead you want to delete.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • success
    Success
    boolean

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/pipedrive-delete-lead
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-delete-lead' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "success": true
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Delete Lead (Pipedrive)→Get Deals by Person (Pipedrive)→Search Deals (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 → delete lead (pipedrive) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

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

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

Start free →Read the API docs