Pipedrive logo

Delete Person (Pipedrive)

Pipedrive → Delete Person (Pipedrive)

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

Marks a person record as deleted in Pipedrive

Install

Add delete 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-delete-person

When to use this.

The "Delete Person (Pipedrive)" action allows users to mark a person record as deleted within the Pipedrive CRM system. This action requires a single input parameter, the "id" (text), which uniquely identifies the person record to be deleted. Upon execution, the action outputs a "status" (text) indicating success, confirming that the deletion has been initiated. It is important to note that the marked person will remain in the system for 30 days before being permanently deleted. This functionality is essential for maintaining data integrity and compliance, making it useful for CRM management, data cleanup, and user privacy. By leveraging this action, businesses can efficiently manage their contacts and ensure that outdated or irrelevant person records are properly handled within their Pipedrive environment.

Try it

Run a sample request.

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

Delete Person (Pipedrive)

Try it

Person id

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • status
    Status
    number

Integrate

Copy-pasteable snippets.

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

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

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

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

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

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

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

Start free →Read the API docs