> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions/get-ticket-statuses.md).

# Get Ticket Statuses

Fetches all available ticket statuses (pipeline stages) from HubSpot, across all ticket pipelines. Useful for determining the correct stage ID before updating a ticket's status.

**Action identifier:** `get_ticket_statuses`. **Reference checked:** 29 September 2026.

## Inputs

No action inputs. Select the HubSpot connection.

## Output shape

Paths are relative to this action's output. Select them from the builder's variable picker; do not add a `ticket` wrapper to actions that return top-level fields. Nullable property fields and empty defaults are not proof that a value was retrieved.

| Path                  | Type            | Meaning                                                                                    |
| --------------------- | --------------- | ------------------------------------------------------------------------------------------ |
| `results`             | list of objects | Ticket stages across pipelines, without pipeline IDs.                                      |
| `results[].id`        | string          | Stage ID to use as `ticket_status`; verify its pipeline using the steps below.             |
| `results[].label`     | string          | Stage display label; labels can repeat across pipelines.                                   |
| `exists`              | boolean         | True when at least one ticket stage is returned.                                           |
| `llm_triage_metadata` | string          | Text summary of stage labels and IDs, without pipeline IDs; `No entries found` when empty. |

## Behavior and limits

Returns stages across ticket pipelines as a flat `id`/`label` list. Pipeline IDs are not retained in the output. Labels can repeat: verify the intended pipeline before writing a stage. Use actual portal IDs, not a literal label such as “Closed”.

No returned stages gives `exists: false` and metadata `No entries found`.

## Find the correct pipeline and status IDs

1. In HubSpot, open **Settings → Objects**, select **Tickets**, and open **Pipelines**.
2. Open the intended pipeline. Use the code icon to view its internal name — this is the pipeline ID.
3. Hover over the required status and use its code icon to view the internal name — this is the status ID.
4. Match that status ID to `results[].id` from Get Ticket Statuses. Match by ID, since different pipelines can use the same status label.
5. When moving a ticket to another pipeline, set `ticket_pipeline` and the matching `ticket_status` together. Test on a test ticket and verify the resulting pipeline and status in HubSpot.

See [HubSpot’s pipeline setup instructions](https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines) for the settings and internal-name controls.

See [Troubleshooting](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/troubleshooting.md) for request errors and retry behavior, or return to the [action catalog](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions.md).