Gohighlevel logo

Upsert Opportunity (LeadConnector)

GoHighLevel → Upsert Opportunity (LeadConnector)

POST/v1/gohighlevel-upsert-opportunity-post
texau__gohighlevel-upsert-opportunity-postcrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/gohighlevel-upsert-opportunity-post
{
  "pipeline_id": "sample-value",
  "followers_action_type": "sample-value",
  "is_remove_all_followers": true,
  "follower": "sample-value",
  "id": "sample-value",
  "unique_name": "Jane Doe",
  "pipeline_stage_id": "sample-value",
  "status": "sample-value",
  "monetary_value": 1,
  "lost_reason_id": "sample-value",
  "contact_id": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "is_new": true,
    "opportunity_id": "rec_4f3a91",
    "unique_name": "sample",
    "monetary_value": 1,
    "pipeline_id": "rec_4f3a91",
    "pipeline_stage_id": "rec_4f3a91",
    "assigned_to": "sample",
    "status": "valid",
    "created_at": "sample",
    "updated_at": "sample",
    "contact_id": "rec_4f3a91",
    "location_id": "rec_4f3a91"
  }
}

Create a new opportunity or update an existing one using the Upsert endpoint in LeadConnector.

Install

Add upsert 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-upsert-opportunity-post

When to use this.

The "Upsert Opportunity (LeadConnector)" action enables users to efficiently create or update opportunities within a CRM system using the LeadConnector API. This action requires key input parameters such as the pipeline ID, follower action type, and follower contact IDs to manage opportunity followers effectively. Optional parameters like opportunity ID, unique name, pipeline stage ID, and monetary value allow for detailed customization of the opportunity being created or updated. The output includes essential data fields such as opportunity ID, status, and timestamps, providing users with immediate feedback on the action's success. This action is particularly useful for sales teams looking to maintain accurate and up-to-date opportunity records, streamline lead management, and enhance collaboration within their CRM workflows.

Try it

Run a sample request.

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

Upsert Opportunity (LeadConnector)

Try it

The ID of the pipeline (Required).

Action type for followers. Select 'add' or 'remove' (Required).

Set to true to remove all followers (Required).

follower Contact IDs (Required).

The ID of the Opportunity. Provide this to UPDATE an existing record. Leave blank to CREATE a new one.

The name of the opportunity.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • is_new
    Is New
    boolean
  • 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
  • assigned_to
    Assigned To
    nullabletext
  • status
    Status
    text
  • created_at
    Created At
    nullabletext
  • updated_at
    Updated At
    nullabletext
  • contact_id
    Contact Id
    text
  • location_id
    Location Id
    nullabletext

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/gohighlevel-upsert-opportunity-post
curl -X POST 'https://v3-api.texau.com/api/v1/gohighlevel-upsert-opportunity-post' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"pipeline_id":"sample-value","followers_action_type":"sample-value","is_remove_all_followers":true,"follower":"sample-value","id":"sample-value","unique_name":"Jane Doe","pipeline_stage_id":"sample-value","status":"sample-value","monetary_value":1,"lost_reason_id":"sample-value","contact_id":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "is_new": true,
    "opportunity_id": "rec_4f3a91",
    "unique_name": "sample",
    "monetary_value": 1,
    "pipeline_id": "rec_4f3a91",
    "pipeline_stage_id": "rec_4f3a91",
    "assigned_to": "sample",
    "status": "valid",
    "created_at": "sample",
    "updated_at": "sample",
    "contact_id": "rec_4f3a91",
    "location_id": "rec_4f3a91"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Upsert Opportunity (LeadConnector)→Update Opportunity Status (LeadConnector)→Get 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 → upsert opportunity (leadconnector) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

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

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

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

Start free →Read the API docs