Gohighlevel logo

Get Opportunity (LeadConnector)

GoHighLevelGet Opportunity (LeadConnector)

POST/v1/gohighlevel-get-opportunity
texau__gohighlevel-get-opportunitycrm
cURL · api.texau.app
84ms
POST/v1/gohighlevel-get-opportunity
{
  "opportunity_id": "sample-value"
}
200 Accepted
{
  "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"
  }
}

Get details of a specific opportunity by its ID in LeadConnector.

Install

Add get 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.

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

Tool name: texau__gohighlevel-get-opportunity

When to use this.

The "Get Opportunity" action in LeadConnector allows users to retrieve detailed information about a specific sales opportunity using its unique ID. This action requires the input parameter "opportunityId," which is essential for identifying the opportunity to be fetched. Upon execution, the action returns a comprehensive set of output fields, including opportunity ID, name, monetary value, pipeline and stage IDs, status, source, and various timestamps related to the opportunity's lifecycle. Additional details such as contact information, notes, tasks, and calendar events are also provided, enabling users to gain insights into the opportunity's context and history. This action is particularly useful for CRM applications, sales tracking, and lead management, helping businesses streamline their sales processes and enhance customer engagement.

Try it

Run a sample request.

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

Get Opportunity (LeadConnector)

Try it

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

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • opportunity_id
    Opportunity Id
    text
  • unique_name
    Unique Name
    text
  • monetary_value
    Monetary Value
    number
  • pipeline_id
    Pipeline Id
    text
  • pipeline_stage_id
    Pipeline Stage Id
    text
  • status
    Status
    text
  • source
    Source
    nullabletext
  • last_status_change_at
    Last Status Change At
    nullabletext
  • last_stage_change_at
    Last Stage Change At
    nullabletext
  • last_action_date
    Last Action Date
    nullabletext
  • index_version
    Index Version
    nullablenumber
  • created_at
    Created At
    nullabletext
  • updated_at
    Updated At
    nullabletext
  • contact_id
    Contact Id
    text
  • location_id
    Location Id
    nullabletext
  • contact_ref_id
    Contact Ref Id
    nullabletext
  • contact_name
    Contact Name
    text
  • contact_company_name
    Contact Company Name
    nullabletext
  • contact_email
    Contact Email
    text
  • contact_mobile_number
    Contact Mobile Number
    nullabletext
  • contact_tag
    Contact Tag
    nullabletext
  • note
    Note
    nullabletext
  • task
    Task
    nullabletext
  • calendar_event
    Calendar Event
    nullabletext
  • lost_reason_id
    Lost Reason Id
    nullabletext
  • follower
    Follower
    nullabletext

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/gohighlevel-get-opportunity
curl -X POST 'https://v3-api.texau.com/api/v1/gohighlevel-get-opportunity' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"opportunity_id":"sample-value"}'
200 Accepted
{
  "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"
  }
}

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Opportunity (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.

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 Get Opportunity (LeadConnector) in 60 seconds.

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