Pipedrive logo

Remove Person from Deal (Pipedrive)

Pipedrive → Remove Person from Deal (Pipedrive)

POST/v1/pipedrive-remove-deal-participant
texau__pipedrive-remove-deal-participantcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/pipedrive-remove-deal-participant
{
  "deal_id": 1,
  "deal_participant_id": 1
}
200 Accepted
{
  "ok": true,
  "data": {
    "success": true,
    "id": "rec_4f3a91"
  }
}

Removes a participant from a deal

Install

Add remove person from deal (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-remove-deal-participant

When to use this.

The "Remove Person from Deal" action in Pipedrive allows users to efficiently remove a participant from a specific deal within their CRM system. This action requires two key input parameters: the deal_id, which identifies the deal from which the participant will be removed, and the deal_participant_id, which is the unique identifier for the participant record to be deleted (not to be confused with the person_id). Upon successful execution, the action returns a success boolean indicating whether the removal was successful, along with the deleted Participant Record ID. This functionality is essential for maintaining accurate deal participant lists, making it particularly useful for sales teams managing dynamic deal structures in their CRM. The action falls under the CRM category, streamlining participant management and enhancing overall deal organization.

Try it

Run a sample request.

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

Remove Person from Deal (Pipedrive)

Try it

The ID of the deal.

The specific ID of the participant record to delete (NOT the person_id).

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
  • id
    Id
    number

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/pipedrive-remove-deal-participant. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/pipedrive-remove-deal-participant
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-remove-deal-participant' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"deal_id":1,"deal_participant_id":1}'
200 Accepted
{
  "ok": true,
  "data": {
    "success": true,
    "id": "rec_4f3a91"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

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

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

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

Start free →Read the API docs