HubSpot: Fetch Pipelines

List the pipelines and stages for HubSpot deals, tickets, or another object type, with their stage IDs.

Tool ID: hubspot_fetch_pipelines

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'hubspot_fetch_pipelines',
  {
    "objectType": "example"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute hubspot_fetch_pipelines --input '{
  "objectType": "example"
}' --json

Example response

The static output schema lacks the details for a reliable example. Use deepline describe hubspot_fetch_pipelines --json for the complete live contract.

Input reference

List HubSpot pipelines for the provided object type.

Name	Type	Required	Default	Details
`payload.objectType`	`string`	No	—	—

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.pipelines`	`array`	Yes	—	—
`result.data.pipelines[].label`	`string`	Yes	—	—
`result.data.pipelines[].displayOrder`	`number`	Yes	—	—
`result.data.pipelines[].id`	`string`	Yes	—	—
`result.data.pipelines[].stages`	`array`	Yes	—	—
`result.data.pipelines[].stages[].label`	`string`	Yes	—	—
`result.data.pipelines[].stages[].displayOrder`	`number`	Yes	—	—
`result.data.pipelines[].stages[].metadata`	`record`	Yes	—	Pipeline-stage metadata. Deal stages commonly include probability. ticket stages commonly include ticketState.
`result.data.pipelines[].stages[].id`	`string`	Yes	—	—
`result.data.pipelines[].stages[].createdAt`	`string`	Yes	—	—
`result.data.pipelines[].stages[].updatedAt`	`string`	Yes	—	—
`result.data.pipelines[].stages[].archived`	`boolean`	Yes	—	—
`result.data.pipelines[].stages[].writePermissions`	`string`	Yes	—	—
`result.data.pipelines[].createdAt`	`string`	Yes	—	—
`result.data.pipelines[].updatedAt`	`string`	Yes	—	—
`result.data.pipelines[].archived`	`boolean`	Yes	—	—
`result.meta`	`record`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation