***

title: Flows commands
approved: 2026-03-16T00:00:00.000Z
topictype: reference
slug: docs/postman-cli/postman-cli-flows
max-toc-depth: 2
----------------

This topic covers flows management commands for the [Postman CLI](/docs/postman-cli/postman-cli-overview/). You can use the `postman flows` commands to run, manage, and analyze flows.

## `postman flows list`

The `postman flows list` command lists the flows available in a workspace. Specify the workspace by its ID.

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows list --workspace <workspace-id>
```

### Options

<ParamField path="-w, --workspace [workspace-id]">
  Specifies the workspace by its ID. This option is required for the `postman flows list` command.
</ParamField>

### Example

```plaintext
postman flows list --workspace ab12a1bb-1a12-1234-123a-123ab1234a1a
```

## `postman flows trigger`

You can use the `postman flows trigger` command to trigger a [deployed](/docs/postman-flows/reference/flows-actions-overview/) flow to run. The deployed flow must have a [request trigger](/docs/postman-flows/reference/blocks/request/). This command requires the flow's ID as an argument. You can also assign values to the flow's inputs with the `--input` option.

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows trigger <flow-id> [options]
```

<ParamField path="<flow-id>">
  The unique identifier of the flow to trigger.
</ParamField>

### Options

<ParamField path="--input [key=value/path.json]">
  Set flow inputs with key=value pairs and/or paths to JSON files.
</ParamField>

### Example

```plaintext
postman flows trigger 12ab12a1ab123ab1234a1234
```

## `postman flows deploy`

You can use the `postman flows deploy` command to [deploy](/docs/postman-flows/build-flows/structure/actions/) a flow to the Postman cloud. This command requires the flow's ID as an argument and the `--path` option. The `--path` option is the URL segment for the trigger, and must be unique for the team. For example, in the URL `deployed-flow.flows.pstmn.io/api/default/new-flow`, the path is `/new-flow`.

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows deploy <flow-id> --path <path>
```

<ParamField path="<flow-id>">
  The unique identifier of the flow to deploy.
</ParamField>

<ParamField path="--path <path>">
  Specifies the path that will be added to the domain where the flow is deployed. This option is required for the `postman flows deploy` command.
</ParamField>

### Example

```plaintext
postman flows deploy 12ab1ab1a1234567890a1234 --path deployed-flow-path
```

## `postman flows run`

This command runs a single flow from your local repo. The flow runs requests and logic blocks entirely locally on your machine, making it ideal for CI/CD workflows. Successful runs return status and output. The `postman flows run` command has options to set [input values](/docs/postman-flows/build-flows/configure/scenarios/#start-block-inputs), show [run log](/docs/postman-flows/build-flows/troubleshoot/troubleshoot/#run-logs) information, and use values from a [scenario](/docs/postman-flows/build-flows/configure/scenarios/). This command requires the local flow's file path as an argument.

<Note class="plan">
  The `postman flows run` command is available with [Postman Enterprise plans](https://www.postman.com/pricing/).
</Note>

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows run <flow-file-path> [options]
```

<ParamField path="<flow-file-path>">
  The local file path to the flow JSON file to run.
</ParamField>

### Options

<ParamField path="-x, --suppress-exit-code">
  Specify whether to override the default exit code for the current run.
</ParamField>

<ParamField path="--verbose">
  Show detailed information about the flow run and each request (method, URL, assertions).
</ParamField>

<ParamField path="--input [key=value/path.json]">
  Set flow inputs with key=value pairs and/or paths to JSON files.
</ParamField>

<ParamField path="--input-file [path.json]">
  Set flow inputs from JSON files.
</ParamField>

<ParamField path="--scenario [name]">
  Reference a pre-built scenario as flow inputs by its name. Can be combined with `--input` to override values.
</ParamField>

### Examples

```bash wordWrap
postman flows run postman/flows/[flow-filename].json

postman flows run postman/flows/[flow-filename].json --input [input name]=[value]

postman flows run postman/flows/[flow-filename].json --input path/to/[input-filename].json

postman flows run postman/flows/[flow-filename].json --scenario "[scenario name]"

postman flows run postman/flows/[flow-filename].json --scenario "[scenario name]" --input [input name]=[value]
```

Learn more at [Postman Flows overview](/docs/postman-flows/flows-overview/).

## `postman flows update`

You can use the `postman flows update` command to update auth and online/offline settings for a deployed flow. This command requires the flow's ID as an argument.

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows update <flow-id> [options]
```

<ParamField path="<flow-id>">
  The unique identifier of the deployed flow to update.
</ParamField>

### Options

<ParamField path="--trigger [on/off]">
  Sets the deployed flow's status to online (`on`) or offline (`off`).
</ParamField>

<ParamField path="--auth [on/off]">
  Turns the flow's authentication setting on or off.
</ParamField>

### Example

```bash
postman flows update 12ab1ab1a1234567890a1234 --trigger on --auth off
```

## `postman flows list-runs`

You can use the `postman flows list-runs` command to fetch run history for a deployed flow in a specified workspace. The result displays the run's timestamp, ID, duration, status, and flow name in a table. This command requires the `--workspace` option.

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows list-runs --workspace <workspace-id> [options]
```

### Options

<ParamField path="-w, --workspace [workspace-id]">
  Specifies the workspace by its ID. This option is required for the `postman flows list-runs` command.
</ParamField>

<ParamField path="--flow [flow-id]">
  Filter by flow ID.
</ParamField>

<ParamField path="--range [time-range]" default="1h">
  Specifies the time window in minutes (`1m`), hours (`1h`), or days (`1d`).
</ParamField>

### Example

```plaintext wordWrap
postman flows list-runs --workspace ab12a1bb-1a12-1234-123a-123ab1234a1a --range 1d
```

## `postman flows get-run`

You can use the `postman flows get-run` command to analyze a specific run.

<Info>
  To use this command, sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).
</Info>

### Usage

```bash
postman flows get-run --run-id <run-id> [options]
```

### Options

<ParamField path="--run-id [run-id]">
  Specifies the run by its ID. This option is required for the `postman flows get-run` command.
</ParamField>

<ParamField path="--logs">
  Shows the full event log including each block's ID, input, and output.
</ParamField>

<ParamField path="--filter [block-id]">
  Narrows output by block ID.
</ParamField>

### Example

```bash
postman flows get-run main/1a123ab1
```