Pipedrive logo

Update Lead (Pipedrive)

Pipedrive → Update Lead (Pipedrive)

POST/v1/pipedrive-update-lead
texau__pipedrive-update-leadcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/pipedrive-update-lead
{
  "id": "sample-value",
  "title": "sample-value",
  "person_id": 1,
  "organization_id": "Acme, Inc.",
  "label_id": "sample-value",
  "value_amount": 1,
  "value_currency": "sample-value",
  "expected_close_date": "sample-value",
  "visible_to": "sample-value",
  "was_seen": true,
  "channel": "sample-value",
  "channel_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "title": "sample",
    "owner_id": "rec_4f3a91",
    "creator_id": "rec_4f3a91",
    "value_amount": 1,
    "value_currency": "sample",
    "expected_close_date": "sample",
    "person_id": "rec_4f3a91",
    "organization_id": "rec_4f3a91",
    "is_archived": true,
    "source_name": "sample",
    "was_seen": true,
    "update_time": "sample",
    "label_id": "rec_4f3a91"
  }
}

Updates one or more properties of a lead in Pipedrive

Install

Add update 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-update-lead

When to use this.

The "Update Lead (Pipedrive)" action allows users to efficiently update one or more properties of a lead within the Pipedrive CRM system. Key input parameters include the lead's unique UUID (id), optional fields such as title, person_id, organization_id, and value_amount, which enable users to modify relevant lead details. This action can also update visibility settings, expected close dates, and marketing channel information. The output includes essential lead data such as the updated lead ID, title, owner ID, and value currency, along with flags indicating whether the lead has been seen or archived. Use cases for this action include maintaining accurate lead information, adjusting potential deal values, and managing lead visibility, making it a vital tool for CRM management and sales pipeline optimization.

Try it

Run a sample request.

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

Update Lead (Pipedrive)

Try it

The UUID of the lead you want to update.

The name of the lead.

The ID of the person this lead is linked to.

The ID of the organization this lead is linked to.

Select a lead label.

The potential monetary value of the lead.

Response is cached — no live API call.

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
    number
  • creator_id
    Creator Id
    nullablenumber
  • value_amount
    Value Amount
    number
  • value_currency
    Value Currency
    text
  • expected_close_date
    Expected Close Date
    nullabletext
  • person_id
    Person Id
    number
  • organization_id
    Organization Id
    number
  • is_archived
    Is Archived
    nullableboolean
  • source_name
    Source Name
    nullabletext
  • was_seen
    Was Seen
    nullableboolean
  • update_time
    Update Time
    nullabletext
  • label_id
    Label Id
    nullabletext

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/pipedrive-update-lead
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-update-lead' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"id":"sample-value","title":"sample-value","person_id":1,"organization_id":"Acme, Inc.","label_id":"sample-value","value_amount":1,"value_currency":"sample-value","expected_close_date":"sample-value","visible_to":"sample-value","was_seen":true,"channel":"sample-value","channel_id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "title": "sample",
    "owner_id": "rec_4f3a91",
    "creator_id": "rec_4f3a91",
    "value_amount": 1,
    "value_currency": "sample",
    "expected_close_date": "sample",
    "person_id": "rec_4f3a91",
    "organization_id": "rec_4f3a91",
    "is_archived": true,
    "source_name": "sample",
    "was_seen": true,
    "update_time": "sample",
    "label_id": "rec_4f3a91"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Update Lead (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 → update lead (pipedrive) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

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

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

Start free →Read the API docs