# List workflows

URL: https://docs.hanzo.ai/docs/openapi/git/get-git-workflows

> Reports the workflows a repository declares at a ref and which declared pool would execute each job — the answer to "would a push here run, and where".

`GET /v1/git/workflows`

> [Git →](https://docs.hanzo.ai/docs/openapi/git) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                         |
| ------------- | --------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/git/workflows` |
| **Method**    | `GET`                                   |
| **Operation** | `get_git_workflows`                     |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`  |

Reports the workflows a repository declares at a ref and which
declared pool would execute each job — the answer to "would a push here run,
and where".

## Request

2 fields.

| Field  | In    | Type   | Required | Description                                                 |
| ------ | ----- | ------ | -------- | ----------------------------------------------------------- |
| `repo` | query | string | —        | Repo is the repository whose workflows to read.             |
| `ref`  | query | string | —        | Ref is the branch to read them at; empty means the default. |

## Response

| Status    | Body             | Meaning |
| --------- | ---------------- | ------- |
| `200`     | git.workflowList | ok      |
| `default` | problem-details  | refused |

`200` body — 7 fields.

| Field                  | In   | Type                | Always | Description                                                                                                                                 |
| ---------------------- | ---- | ------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| `data`                 | body | git.workflowView\[] | —      | Data is the workflows the repository declares at the ref.                                                                                   |
| `data[].fault`         | body | string              | —      | Fault is why this document cannot run at all, when it cannot be read.                                                                       |
| `data[].jobs`          | body | git.jobView\[]      | —      | Jobs is what it declares, and where each would run.                                                                                         |
| `data[].jobs[].name`   | body | string              | —      | Name is the job's id in the workflow document.                                                                                              |
| `data[].jobs[].pool`   | body | string              | —      | Pool is the declared pool carrying every one of those labels, or empty when no pool does — which is the answer to "why is nothing running". |
| `data[].jobs[].runsOn` | body | string\[]           | —      | RunsOn is the labels the job asked for.                                                                                                     |
| `data[].name`          | body | string              | —      | Name is the document's path in the repository.                                                                                              |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo git workflows
```

**SDK**

**.ts**

```ts
import { Configuration, GitApi } from 'hanzoai';

const api = new GitApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getGitWorkflows();
```

**.py**

```python
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import GitApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = GitApi(client).get_git_workflows()
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.GitAPI.GetGitWorkflows(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::apis::{configuration::Configuration, git_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = git_api::get_git_workflows(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.GitApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new GitApi(client).getGitWorkflows();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/git/workflows \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **git** through the `git` tool, which names its 38 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_git_keys"
         }
       }
     }'
```

---

[Git API](https://docs.hanzo.ai/docs/openapi/git) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)