Gohighlevel logo

Update Opportunity Status (LeadConnector)

GoHighLevel → Update Opportunity Status (LeadConnector)

POST/v1/gohighlevel-update-opportunity-status
texau__gohighlevel-update-opportunity-statuscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/gohighlevel-update-opportunity-status
{
  "id": "sample-value",
  "status": "sample-value",
  "lost_reason_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "success": true
  }
}

Update the status of a specific opportunity in LeadConnector.

Install

Add update opportunity status (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.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__gohighlevel-update-opportunity-status

When to use this.

The "Update Opportunity Status" action in LeadConnector allows users to efficiently modify the status of a specific opportunity within their CRM system. This action requires two key input parameters: the unique identifier (id) of the opportunity to be updated and the new status (status) to assign, ensuring precise updates. An optional parameter, lostReasonId, can be provided if the opportunity's status is changed to 'lost', allowing for better tracking of lost opportunities. The output field indicates whether the update succeeded (succeeded), providing immediate feedback on the operation's success. This action is essential for sales teams looking to maintain accurate opportunity tracking and reporting, making it a vital tool in customer relationship management (CRM) workflows.

Try it

Run a sample request.

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

Update Opportunity Status (LeadConnector)

Try it

The ID of the Opportunity you want to update (Required).

The new status of the opportunity (Required).

The ID of the reason the opportunity was lost (only applicable if status is 'lost').

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

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/gohighlevel-update-opportunity-status. Auth: x-api-key.

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

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Update Opportunity Status (LeadConnector)→Get Business/Company (LeadConnector)→Create Business/Company (LeadConnector)

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 opportunity status (leadconnector) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Update Opportunity Status (LeadConnector)GoHighLevel 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 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.

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 GoHighLevel 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__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 Status (LeadConnector) in 60 seconds.

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

Start free →Read the API docs