> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/harness.md).

# Harness

Harness is a CI/CD and software delivery platform. Read pipelines and read or trigger pipeline executions from your AI workflows.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector         | Authentication |
| ----------------- | -------------- |
| Harness (API Key) | API key        |

#### Harness (API Key)

Connect to Harness to read pipelines and read or trigger executions.

**Set up in Harness**

1. Prepare the Harness account or service that the workflow will access. Grant access to the required resources and operations.
2. **Account identifier:** Your Harness account identifier (from the account settings or the app URL).

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Harness (API Key)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field           | Required | What to enter                                                                                                                                                                                                                                                               |
| ----------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API key                 | Yes      | A Harness API key (personal or service-account token) with pipeline view and, to trigger runs, execute permissions. Use the token value, not the API key name. [Provider instructions](https://developer.harness.io/docs/platform/automation/api/add-and-manage-api-keys/). |
| Account identifier      | Yes      | Your Harness account identifier (from the account settings or the app URL).                                                                                                                                                                                                 |
| Organization identifier | Yes      | The Harness organization identifier, e.g. default.                                                                                                                                                                                                                          |
| Project identifier      | Yes      | The Harness project identifier that owns the pipelines you want to use.                                                                                                                                                                                                     |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Harness** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### List Pipelines

List the pipelines in the connected Harness project.

**Inputs**

| Field           | Type    | Required | Description                                                      |
| --------------- | ------- | -------- | ---------------------------------------------------------------- |
| Maximum results | integer | No       | Maximum pipelines to return (1-5000). Minimum: 1. Maximum: 5000. |

**Outputs**

| Field     | Type        | Description                                 |
| --------- | ----------- | ------------------------------------------- |
| Pipelines | dict\_array | Pipelines in the connected Harness project. |
| Count     | integer     | Number of pipelines returned.               |

#### Get Pipeline

Get summary details for a single Harness pipeline.

**Inputs**

| Field               | Type            | Required | Description                                                                                                                                                                                      |
| ------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Pipeline identifier | select (string) | Yes      | The pipeline's identifier (not its display name). Options are loaded from the connected project (up to 100). Enter an identifier if it is not listed. Options load from the selected connection. |

**Outputs**

| Field            | Type    | Description                                                   |
| ---------------- | ------- | ------------------------------------------------------------- |
| Identifier       | string  | The pipeline's identifier.                                    |
| Name             | string  | The pipeline's display name.                                  |
| Description      | string  | The pipeline's description.                                   |
| Number of stages | integer | Number of stages reported by Harness, or null if unavailable. |

#### List Pipeline Executions

List recent pipeline executions in the connected Harness project.

**Inputs**

| Field               | Type            | Required | Description                                                                                                                                                                                             |
| ------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pipeline identifier | select (string) | No       | Optionally filter executions to one pipeline identifier. Options are loaded from the connected project (up to 100). Enter an identifier if it is not listed. Options load from the selected connection. |
| Maximum results     | integer         | No       | Maximum executions to return (1-5000). Minimum: 1. Maximum: 5000.                                                                                                                                       |

**Outputs**

| Field      | Type        | Description                                          |
| ---------- | ----------- | ---------------------------------------------------- |
| Executions | dict\_array | Recent pipeline executions in the connected project. |
| Count      | integer     | Number of executions returned.                       |

#### Get Pipeline Execution

Get details for a single Harness pipeline execution.

**Inputs**

| Field        | Type            | Required | Description                                                                                                                               |
| ------------ | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Execution ID | select (string) | Yes      | Select one of up to 100 recent runs, enter an execution ID, or use an Execute Pipeline output. Options load from the selected connection. |

**Outputs**

| Field               | Type   | Description                              |
| ------------------- | ------ | ---------------------------------------- |
| Execution ID        | string | The run's plan execution ID.             |
| Pipeline identifier | string | The identifier of the pipeline that ran. |
| Name                | string | The execution's display name.            |
| Status              | string | The execution's current status.          |

#### Execute Pipeline

Start a pipeline run. This executes pipeline steps and may consume Harness credits.

**Inputs**

| Field               | Type            | Required | Description                                                                                                                                                                           |
| ------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pipeline identifier | select (string) | Yes      | The identifier of the pipeline to run. Options are loaded from the connected project (up to 100). Enter an identifier if it is not listed. Options load from the selected connection. |
| Module              | select (string) | No       | Optional Harness module. Leave empty unless your pipeline requires it. Available values: CD, CI, CF, STO, CE, CV, IACM, CHAOS, IDP.                                                   |
| Runtime input YAML  | textarea        | No       | Optional YAML supplying the selected pipeline's runtime inputs. Leave empty if no inputs are required. This does not replace the stored pipeline.                                     |

**Outputs**

| Field        | Type   | Description                            |
| ------------ | ------ | -------------------------------------- |
| Execution ID | string | The triggered run's plan execution ID. |
| Status       | string | The triggered run's initial status.    |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/harness.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
