Skip to main content
OPP

Opportunity CRUD

Pipelines & Opportunities · Intermediate · Updated March 2026

Create, read, update, and delete sales opportunities with monetary values, pipeline stage assignment, and contact association via MCP.

Opportunities are where contacts become revenue. Every deal in your pipeline is an opportunity record with a value, a stage, an owner, and a contact association. Managing opportunities through MCP means you can create deals automatically when external events happen — a form submission, a calendar booking, a payment initiation — without relying solely on GHL workflows to catch every trigger.

What This MCP Tool Does

Full CRUD operations on opportunity (deal) records. Create new opportunities with monetary values and pipeline stage assignment, retrieve opportunity details, update any field on an opportunity, and delete opportunities. Every opportunity is linked to a contact and lives within a pipeline.

Endpoint Reference

Create an opportunity: POST /opportunities Creates a new deal in a specific pipeline stage with an assigned value and contact.

Get an opportunity: GET /opportunities/{opportunityId} Retrieve the full opportunity record including value, stage, status, contact association, and metadata.

Update an opportunity: PUT /opportunities/{opportunityId} Modify any field — move to a different stage, change the value, reassign ownership, update the expected close date.

Delete an opportunity: DELETE /opportunities/{opportunityId} Permanently remove the opportunity record.

Authentication

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

Key Parameters

  • pipelineId — which pipeline the opportunity belongs to
  • pipelineStageId — the current stage within the pipeline
  • contactId — the contact associated with the deal
  • name — opportunity name/title
  • monetaryValue — deal value in dollars
  • status — open, won, lost, or abandoned
  • assignedTo — team member user ID responsible for the deal
  • source — where the opportunity came from

Important Notes

Pipeline and stage IDs are required for creation. Use Pipeline Getter to retrieve the available pipelines and their stage IDs before creating opportunities.

Moving an opportunity to a different stage via the update endpoint triggers the same workflow conditions as manual stage movement in the UI. If you have a workflow that fires when a deal enters a specific stage, updating via MCP triggers it.

Opportunity values are stored as numbers. Include only the numeric value, not currency symbols or formatting.

Opportunities can have custom fields just like contacts. The same Contact Fields pattern applies — use field IDs, not names.

Common Questions

Can I create an opportunity without a contact? A contact association is required. Every deal must be linked to a contact record.

Do stage changes via MCP trigger workflows? Yes. Stage-change triggers fire regardless of whether the change was made through the UI, a workflow action, or an MCP call.

Can an opportunity exist in multiple pipelines? No. Each opportunity belongs to exactly one pipeline. If you need to track a deal across multiple processes, create separate opportunities in each pipeline.

How do I move a deal to “Won” status? Use either the update endpoint to change the status field, or the Status Manager endpoint for explicit status transitions.