Skip to main content
GHL MCP Guide
PPL

Pipeline Getter

Pipelines & Opportunities · Basic · Updated March 2026

Retrieve all sales pipelines with their stages, configurations, and settings. Essential for mapping deal data to the correct pipeline structure.

Before you can create opportunities, move deals between stages, or build pipeline reports, you need to know what pipelines exist and what stages they contain. Pipeline Getter retrieves the complete pipeline structure for a location — names, stage IDs, stage ordering, and configuration. It’s the reference data that every other opportunity operation depends on.

What This MCP Tool Does

Retrieve all sales pipelines configured in a location along with their stages, ordering, and settings. This is a read-only tool — you’re getting the pipeline structure, not modifying it. The data returned here provides the pipeline IDs and stage IDs required by Opportunity CRUD, Opportunity Upsert, and Status Manager.

Endpoint Reference

List all pipelines: GET /opportunities/pipelines Returns every pipeline in the location with complete stage definitions.

Authentication

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

Response Data

Each pipeline includes:

  • id — pipeline ID (used in opportunity creation and search)
  • name — display name
  • stages — array of stage objects, each with:
    • id — stage ID (used in opportunity creation and movement)
    • name — stage display name
    • position — sort order

Important Notes

Pipeline and stage IDs are unique to each location. A pipeline called “Sales Pipeline” in one sub-account has a completely different ID than a pipeline with the same name in another sub-account. Never hardcode pipeline or stage IDs across locations.

This endpoint is read-only through MCP. Creating or modifying pipelines requires the GHL UI. Plan your pipeline structure before building integrations that depend on specific stages.

Cache pipeline data if you’re making multiple opportunity operations. The pipeline structure rarely changes, so fetching it once and reusing the IDs is more efficient than calling this endpoint before every opportunity operation.

Stage order matters. When building pipeline reports or visualizations, use the position field to display stages in their intended sequence.

Common Questions

Can I create or modify pipelines through MCP? No. Pipeline configuration is UI-only. MCP provides read access to the structure.

How often does pipeline structure change? Rarely, unless your client actively reorganizes their sales process. It’s safe to cache pipeline data for the duration of a session or batch operation.

Can a location have multiple pipelines? Yes. Many businesses run separate pipelines for different services, client types, or sales processes. The getter returns all of them.

How do I map stage names to IDs? The response includes both. Iterate through the stages array, match on name, and use the corresponding ID for opportunity operations.

Back to GHL MCP Guide