Update Opportunity (LeadConnector)
GoHighLevel → Update Opportunity (LeadConnector)
/v1/gohighlevel-update-opportunity{ "id": "sample-value", "unique_name": "Jane Doe", "pipeline_id": "sample-value", "pipeline_stage_id": "sample-value", "status": "sample-value", "monetary_value": 1 }
{ "ok": true, "data": { "opportunity_id": "rec_4f3a91", "unique_name": "sample", "monetary_value": 1, "pipeline_id": "rec_4f3a91", "pipeline_stage_id": "rec_4f3a91", "status": "valid", "source": "sample", "last_status_change_at": "valid", "last_stage_change_at": "sample", "last_action_date": "sample", "index_version": 1, "created_at": "sample", "updated_at": "sample", "contact_id": "rec_4f3a91", "location_id": "rec_4f3a91", "contact_ref_id": "rec_4f3a91", "contact_name": "sample", "contact_company_name": "sample", "contact_email": "[email protected]", "contact_mobile_number": "sample", "contact_tag": "sample", "note": "sample", "task": "sample", "calendar_event": "sample", "lost_reason_id": "rec_4f3a91", "follower": "sample" } }
Update an existing opportunity in LeadConnector.
Install
Add update opportunity (leadconnector) to your MCP client.
Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__gohighlevel-update-opportunity
When to use this.
The "gohighlevel-update-opportunity" action allows users to efficiently update existing opportunities within the LeadConnector CRM platform. This action requires the unique ID of the opportunity to be updated and offers optional parameters such as the opportunity name, pipeline ID, pipeline stage ID, status, and monetary value to refine the update process. Upon execution, it returns comprehensive output data, including the updated opportunity ID, name, monetary value, pipeline details, status, contact information, and timestamps for various actions. This functionality is essential for sales teams looking to maintain accurate records of their leads and opportunities, streamline their sales processes, and enhance customer relationship management. Use cases include updating lead statuses, adjusting monetary values based on negotiations, and tracking changes in opportunity stages, making it a vital tool for effective CRM management.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Update Opportunity (LeadConnector)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
opportunity_idOpportunity Idtextunique_nameUnique Nametextmonetary_valueMonetary Valuenumberpipeline_idPipeline Idtextpipeline_stage_idPipeline Stage IdtextstatusStatustextsourceSourcenullabletextlast_status_change_atLast Status Change Atnullabletextlast_stage_change_atLast Stage Change Atnullabletextlast_action_dateLast Action Datenullabletextindex_versionIndex Versionnullablenumbercreated_atCreated Atnullabletextupdated_atUpdated Atnullabletextcontact_idContact Idtextlocation_idLocation Idnullabletextcontact_ref_idContact Ref Idnullabletextcontact_nameContact Namenullabletextcontact_company_nameContact Company Namenullabletextcontact_emailContact Emailnullabletextcontact_mobile_numberContact Mobile Numbernullabletextcontact_tagContact TagnullabletextnoteNotenullabletexttaskTasknullabletextcalendar_eventCalendar Eventnullabletextlost_reason_idLost Reason IdnullabletextfollowerFollowernullabletext
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/gohighlevel-update-opportunity. Auth: x-api-key.
/v1/gohighlevel-update-opportunitycurl -X POST 'https://v3-api.texau.com/api/v1/gohighlevel-update-opportunity' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"id":"sample-value","unique_name":"Jane Doe","pipeline_id":"sample-value","pipeline_stage_id":"sample-value","status":"sample-value","monetary_value":1}'
{ "ok": true, "data": { "opportunity_id": "rec_4f3a91", "unique_name": "sample", "monetary_value": 1, "pipeline_id": "rec_4f3a91", "pipeline_stage_id": "rec_4f3a91", "status": "valid", "source": "sample", "last_status_change_at": "valid", "last_stage_change_at": "sample", "last_action_date": "sample", "index_version": 1, "created_at": "sample", "updated_at": "sample", "contact_id": "rec_4f3a91", "location_id": "rec_4f3a91", "contact_ref_id": "rec_4f3a91", "contact_name": "sample", "contact_company_name": "sample", "contact_email": "[email protected]", "contact_mobile_number": "sample", "contact_tag": "sample", "note": "sample", "task": "sample", "calendar_event": "sample", "lost_reason_id": "rec_4f3a91", "follower": "sample" } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
crm
Update Opportunity Status (LeadConnector)
Update the status of a specific opportunity in LeadConnector.
Get Business/Company (LeadConnector)
Retrieves the details of a specific standalone Business (Company) record using its ID.
Create Business/Company (LeadConnector)
Creates a new standalone Business (Company) record in GoHighLevel.
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 opportunity (leadconnector) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
Reliability
Rate limits & reliability.
- Per-minute limit60 / min
- Per-day limit10,000 / day
- 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. |
Related
More GoHighLevel actions.
Update Opportunity Status (LeadConnector)
Update the status of a specific opportunity in LeadConnector.
Get Business/Company (LeadConnector)
Retrieves the details of a specific standalone Business (Company) record using its ID.
Create Business/Company (LeadConnector)
Creates a new standalone Business (Company) record in GoHighLevel.
Upsert Opportunity (LeadConnector)
Create a new opportunity or update an existing one using the Upsert endpoint in LeadConnector.
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__gohighlevel-...` 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 Opportunity (LeadConnector) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.