Skip to main content
GHL MCP Guide
STA

Status Manager

Pipelines & Opportunities · Intermediate · Updated March 2026

Update opportunity pipeline stages and statuses. Manage deal lifecycle transitions that trigger workflow automations and team notifications.

Moving deals through pipeline stages and marking them as won, lost, or abandoned are the most consequential actions in a sales CRM. Every status change can trigger workflows, update forecasts, and notify team members. Status Manager gives you a dedicated endpoint for these transitions, separate from the general opportunity update, making it explicit when you’re changing the outcome of a deal.

What This MCP Tool Does

Update the status of an opportunity (open, won, lost, abandoned) through a dedicated endpoint. Status changes are the highest-impact update on a deal because they trigger pipeline-stage workflows, update revenue forecasts, and generate notifications.

Endpoint Reference

Update opportunity status: PATCH /opportunities/{opportunityId}/status Change the deal’s status. This is a targeted update specifically for status transitions, separate from the general update endpoint on Opportunity CRUD.

Authentication

Requires a Private Integration Token (PIT) with the opportunities scope enabled.

Key Parameters

  • status — the new status: “open”, “won”, “lost”, or “abandoned”
  • pipelineStageId — optional, move to a specific stage alongside the status change

Important Notes

Status changes via MCP trigger the same workflow automations as changes made through the UI. If you have a workflow that fires when a deal is marked “won,” changing status via MCP triggers it.

The distinction between lost and abandoned matters for reporting. “Lost” typically means a competitive loss or a deal that went cold. “Abandoned” means the deal was removed from active consideration without a clear outcome. Your team’s definitions should be consistent.

Moving a deal back to “open” from “won” or “lost” is possible and reopens the opportunity. Be careful with this in reporting contexts — reopened deals can skew win-rate calculations.

Combining a status change with a stage change in a single call is efficient. You can mark a deal as “won” and move it to a “Closed-Won” stage simultaneously.

Common Questions

Can I change status and stage in one call? Yes. Include both status and pipelineStageId in the request to make both changes atomically.

Does marking a deal as “won” affect revenue reporting? Yes. Won deals contribute to revenue totals in GHL’s reporting dashboards and in any data you pull through Opportunity Search.

Can I bulk-update statuses? Not through a single endpoint. Iterate through deals using Opportunity Search and update each one individually.

What triggers when I change a status via MCP? The same triggers that fire through the UI: pipeline stage change workflows, opportunity status change triggers, and any automation conditions that reference deal status.

Back to GHL MCP Guide