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.

Update Person (Pipedrive)

Pipedrive → Update Person (Pipedrive)

POST/v1/pipedrive-update-person

texau__pipedrive-update-personcrm

Run in Studio →Open in MCP

cURL · api.texau.app

84ms

POST/v1/pipedrive-update-person

{
  "person_id": 1,
  "unique_name": "Jane Doe",
  "org_id": "sample-value",
  "email": "[email protected]",
  "email_primary": "[email protected]",
  "email_label": "[email protected]",
  "mobile_number": "sample-value",
  "mobile_number_primary": true,
  "mobile_number_label": "sample-value",
  "visible_to": "sample-value",
  "label_id": "sample-value"
}

200 Accepted

{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "first_name": "sample",
    "owner_id": "rec_4f3a91",
    "org_id": "rec_4f3a91",
    "is_deleted": true,
    "visible_to": 1,
    "add_time": "sample",
    "update_time": "sample",
    "label_id": "rec_4f3a91",
    "primary_email": "[email protected]",
    "primary_mobile_number": "sample"
  }
}

Updates an existing Pipedrive person's name, email, phone, or organization using their person ID.

Install

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

When to use this.

The "Update Person (Pipedrive)" action allows users to modify existing contact details for a person in the Pipedrive CRM system using their unique person ID. This action supports various input parameters, including optional fields such as name, email, phone number, and organization ID, enabling comprehensive updates to a person's profile. Users can also specify primary email and phone status, visibility settings, and assign labels for better organization. The output includes essential data such as the updated person ID, name, owner ID, organization ID, and timestamps for record-keeping. This action is ideal for CRM management, ensuring accurate and up-to-date contact information for effective sales and customer relationship strategies.

Try it

Run a sample request.

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

Update Person (Pipedrive)

Try it

Response

Output schema.

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

FieldType

id
Id
number
unique_name
Unique Name
text
first_name
First Name
text
owner_id
Owner Id
nullablenumber
org_id
Org Id
number
is_deleted
Is Deleted
nullableboolean
visible_to
Visible To
nullablenumber
add_time
Add Time
nullabletext
update_time
Update Time
nullabletext
label_id
Label Id
nullablearray
primary_email
Primary Email
text
primary_mobile_number
Primary Mobile Number
text

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app

84ms

POST/v1/pipedrive-update-person

curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-update-person' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"person_id":1,"unique_name":"Jane Doe","org_id":"sample-value","email":"[email protected]","email_primary":"[email protected]","email_label":"[email protected]","mobile_number":"sample-value","mobile_number_primary":true,"mobile_number_label":"sample-value","visible_to":"sample-value","label_id":"sample-value"}'

200 Accepted

{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "unique_name": "sample",
    "first_name": "sample",
    "owner_id": "rec_4f3a91",
    "org_id": "rec_4f3a91",
    "is_deleted": true,
    "visible_to": 1,
    "add_time": "sample",
    "update_time": "sample",
    "label_id": "rec_4f3a91",
    "primary_email": "[email protected]",
    "primary_mobile_number": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Update 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.

Input	Status	Score
[email protected]	valid	96
[email protected]	risky	54
[email protected]	invalid	12

Workflow

A real example.

Trigger → update person (pipedrive) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.

Step 2Update 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.

Code	Cause	Fix
200 OK	Action ran. Data in `data`.	Read response.
400 Bad Request	Missing or malformed input.	Validate against the input schema.
401 Unauthorized	Missing or invalid `x-api-key`.	Re-issue from /api-platform.
403 Forbidden	Workspace lacks plan tier.	Upgrade or contact sales.
404 Not Found	Action key not recognized.	Verify the slug.
429 Rate Limited	Per-minute or per-day cap hit.	Backoff; reduce concurrency.
500 Server Error	Unexpected TexAu issue.	Retry with backoff.
502 Bad Gateway	Upstream provider 5xx.	Retry; we surface root cause.
504 Timeout	Upstream 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.

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

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

Start free →Read the API docs

Update Person (Pipedrive)

Add update person (pipedrive) to your MCP client.

When to use this.

Run a sample request.

Update Person (Pipedrive)

Output schema.

Copy-pasteable snippets.

How this fits a workflow.

Get Deals by Person (Pipedrive)

Delete Lead (Pipedrive)

Search Deals (Pipedrive)

Results land in a TexAu table.

A real example.

Who runs this.

Rate limits & reliability.

HTTP status codes.

What it costs to run.

More Pipedrive actions.

Get Deals by Person (Pipedrive)

Delete Lead (Pipedrive)

Search Deals (Pipedrive)

Search Organizations (Pipedrive)

FAQ.

Is this real-time?

Do I get charged on failure?

Does it work with Claude / Cursor via MCP?

What CRMs can I push results to?

Run Update Person (Pipedrive) in 60 seconds.