CRM Pipelines

Name: CRM Pipelines API
Brand: CRM Pipelines
Availability: InStock

✓ Official Vendor SpecCRMDeal Pipelineoauth2,apiKey14 EndpointsREST

For Agents

Manage HubSpot CRM pipelines and pipeline stages for any object type, including create, read, update, delete, and full audit history of changes.

Quickstart

Get started with CRM Pipelines in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a hubspot pipeline"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CRM Pipelines API.

Create, read, update, and delete pipelines for deals, tickets, or custom objects

List all pipelines defined for a given object type

Add, update, and remove stages within a pipeline in a defined display order

Retrieve the audit log of every change made to a pipeline

Retrieve the audit log of every change made to a specific pipeline stage

GET STARTED

Start building with CRM Pipelines API

Explore with Jentic

View OpenAPI Document

The HubSpot CRM Pipelines API manages the pipelines and pipeline stages that define how records move through a workflow — sales deals through sales stages, support tickets through resolution stages, and any custom-object pipeline a portal defines. Endpoints cover full CRUD on pipelines and stages, plus dedicated audit endpoints that return the change history for both. Agents can list, read, create, update, and delete pipelines for a given object type, manage the ordered list of stages within each pipeline, and inspect every change made to either through the audit log. Use it to provision pipelines for a new portal, programmatically rename stages without breaking automation, or build governance dashboards from the audit history.

Use Cases

Patterns agents use CRM Pipelines API for, with concrete tasks.

★ Pipeline provisioning for a new portal

Stand up the sales and ticket pipelines a customer needs as part of onboarding a new HubSpot portal. POST /crm/v3/pipelines/{objectType} creates a pipeline, then POST /crm/v3/pipelines/{objectType}/{pipelineId}/stages adds each stage in order. Lets a setup agent reproduce a tested pipeline structure across portals without manual configuration.

POST a new sales pipeline to /crm/v3/pipelines/deals with label='Enterprise Sales' and displayOrder=1, then POST four ordered stages to /crm/v3/pipelines/deals/{pipelineId}/stages.

Stage rename with audit trail

Rename a pipeline stage as the team's process evolves and capture the change in HubSpot's audit log. PATCH /crm/v3/pipelines/{objectType}/{pipelineId}/stages/{stageId} updates the stage label, and GET /crm/v3/pipelines/{objectType}/{pipelineId}/stages/{stageId}/audit returns who made the change and when, so governance teams can trace the modification.

PATCH /crm/v3/pipelines/deals/{pipelineId}/stages/{stageId} setting label to 'Closed Won — Annual', then GET the same stage's /audit endpoint and return the most recent entry.

Pipeline configuration export

Export a portal's pipeline configuration as a structured document for backup, documentation, or migration to another portal. List pipelines per object type, then list stages per pipeline, and serialise the result. Useful for partners managing multiple portals or for disaster-recovery snapshots.

GET /crm/v3/pipelines/deals to list pipelines, then for each pipeline GET /crm/v3/pipelines/deals/{pipelineId}/stages and return the combined configuration as JSON.

AI agent execution through Jentic

An agent that needs to manage pipelines discovers this API via Jentic's intent search using a query like 'create a hubspot pipeline' or 'list pipeline stages', loads the input schema for the chosen operation, and executes the call with credentials supplied from the Jentic vault. Audit endpoints work the same way for read-only governance flows.

Search Jentic for 'create a hubspot pipeline', load POST /crm/v3/pipelines/{objectType}, and execute it for objectType=deals with a label and stages payload.

Key Endpoints

14 endpoints — the hubspot crm pipelines api manages the pipelines and pipeline stages that define how records move through a workflow — sales deals through sales stages, support tickets through resolution stages, and any custom-object pipeline a portal defines.

METHOD

PATH

DESCRIPTION

GET

/crm/v3/pipelines/{objectType}

List all pipelines for an object type

POST

/crm/v3/pipelines/{objectType}

Create a new pipeline for an object type

GET

/crm/v3/pipelines/{objectType}/{pipelineId}

Read a single pipeline by ID

PATCH

/crm/v3/pipelines/{objectType}/{pipelineId}

Update a pipeline's label or display order

DELETE

/crm/v3/pipelines/{objectType}/{pipelineId}

Delete a pipeline

GET

/crm/v3/pipelines/{objectType}/{pipelineId}/stages

List stages for a pipeline

POST

/crm/v3/pipelines/{objectType}/{pipelineId}/stages

Add a stage to a pipeline

GET

/crm/v3/pipelines/{objectType}/{pipelineId}/audit

Read the audit log for a pipeline

GET

/crm/v3/pipelines/{objectType}

List all pipelines for an object type

POST

/crm/v3/pipelines/{objectType}

Create a new pipeline for an object type

GET

/crm/v3/pipelines/{objectType}/{pipelineId}

Read a single pipeline by ID

PATCH

/crm/v3/pipelines/{objectType}/{pipelineId}

Update a pipeline's label or display order

DELETE

/crm/v3/pipelines/{objectType}/{pipelineId}

Delete a pipeline

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

HubSpot OAuth and private app tokens are stored encrypted in the Jentic vault, with scope-checked access for pipeline write operations. The Authorization header is attached at execution time so credentials never appear in agent context.

Intent-based discovery

Agents search by intent (e.g. 'create a hubspot pipeline' or 'list pipeline stages') and Jentic returns the matching Pipelines operation with its JSON Schema, including the objectType path parameter and stage metadata fields.

Time to first call

Direct integration: half a day to wire OAuth, manage stage display ordering, and handle audit pagination. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot CRM Deals

Manages the deal records that move through pipeline stages

Use to create or update the deals that the pipelines configured here will route.

Complementary

HubSpot CRM Tickets

Manages support ticket records that flow through ticket pipelines

Pick this when the pipeline you are configuring is for service or support workflows.

Complementary

HubSpot CRM Objects

Generic CRM record API used to update the pipeline stage property on individual records

Use to move records between the stages defined here without going through type-specific endpoints.

FAQs

Specific to using CRM Pipelines API through Jentic.

What authentication does the HubSpot Pipelines API use?

It accepts OAuth 2.0 access tokens and private app access tokens passed as a Bearer credential in the Authorization header. Pipeline write operations require a token with the appropriate CRM scopes for the target object type.

Which object types support pipelines?

Deals and tickets are the standard supported types, plus any custom object configured for pipeline use. The objectType path parameter on /crm/v3/pipelines/{objectType} accepts these values.

What are the rate limits for the HubSpot Pipelines API?

It shares HubSpot's account-level rate limits, typically 100 requests per 10 seconds for OAuth apps. Pipeline configuration changes are infrequent enough that the standard limits are rarely a constraint.

How do I add a stage to a pipeline through Jentic?

Search Jentic with 'add hubspot pipeline stage', load POST /crm/v3/pipelines/{objectType}/{pipelineId}/stages, and execute it with the stage label, displayOrder, and metadata payload. Jentic returns the new stage's id.

Can I see who changed a pipeline?

Yes. GET /crm/v3/pipelines/{objectType}/{pipelineId}/audit returns a chronological list of changes with the user that made each change. There is also a per-stage audit endpoint at /audit under the stage path.

What happens to deals when I delete a pipeline stage?

Deleting a stage requires that no records are currently in it; HubSpot returns an error if deals or tickets are present. Move records to another stage with a property update before issuing DELETE.