Add Approval Activity
Approve or reject a Harness pipeline approval instance, optionally recording comments and custom approver inputs. Returns the resulting approval instance.
Harness Core CD APIs for managing pipelines, executions, services, environments, infrastructure, input sets, triggers, and templates.
Approve or reject a Harness pipeline approval instance, optionally recording comments and custom approver inputs. Returns the resulting approval instance.
Add tags to a completed Harness pipeline execution. Existing tags are preserved unless a supplied key matches, in which case its value is overwritten.
Check for allowed-values usage in Harness environments for the connected account. Returns the entities using allowed-values and whether all entries were checked. This check does not modify environments.
Check whether a Harness pipeline execution can be retried using its plan execution ID, organization, and project. Returns retry eligibility without starting a retry.
Check whether a Harness service instance can be rolled back using its instance key and infrastructure mapping ID. Returns eligibility, an explanation, and swim lane information without starting a rollback.
Check for allowed-values usage in Harness services in the connected account. Returns service references and whether all entries were checked. This check does not modify services.
Convert an existing Harness sequential pipeline to DAG format by adding depends_on fields to stages. Specify the pipeline, organization, and project. Returns converted pipeline YAML and available validation, governance, Git, and storage metadata.
Create a Production or PreProduction environment in the connected Harness account, with optional organization and project identifiers, display details, tags, and YAML. Returns the created environment, validity details, and governance results when available.
Create a Harness environment group from its YAML definition in the connected account. Optionally specify organization, project, identifier, color, and Old Git Sync selectors. Returns the group, linked environments, and evaluation details.
Create up to 1000 Harness environments in one request with partial success support. Each environment specifies its type and optional scope, display details, tags, and YAML. Returns successful environments, individual failures with scope and error details, and provider totals. A successful batch response can contain failed items; inspect failed before retrying those items.
Create an infrastructure definition in a Harness environment using its YAML specification. YAML alone is sufficient; optional fields supply identifiers, display details, tags, provider type, and service discovery settings. Returns the created infrastructure and available validity, discovery, and governance results.
Create a Harness pipeline input set from its complete YAML definition in a specified organization, project, and pipeline. Supports inline or Git-backed storage and optional branch creation. Returns input set and validity details.
Create a Harness organization in the connected account with optional identifier, name, description, and tags. Returns its details and metadata.
Create an overlay input set for a Harness pipeline from its complete YAML definition, combining referenced input sets. Supports inline or Git-backed storage and optional branch creation. Returns the overlay and validity details.
Create a Harness pipeline from its complete YAML definition in a specified organization and project. Supports inline or Git-backed storage and optional branch creation. Returns the pipeline identifier, governance evaluation, and public access outcome.
Create a Harness pipeline trigger resource from YAML in an organization and project, optionally specifying the user or service account that executes it. Returns saved trigger details and any validation errors.
Create a Harness pipeline trigger from a complete raw YAML definition in an organization and project. Uses the original YAML trigger endpoint; returns saved trigger details and validation diagnostics. To supply an executor identity separately, use Create Pipeline Trigger.
Create a Harness project in the connected account, optionally in a specified organization, with a name, identifier, modules, color, description, and tags. Returns the created project and its metadata.
Create a service in the connected Harness account, with optional organization and project identifiers, name, description, tags, and YAML definition. Returns the created service, validity details, and governance results when available.
Create a Harness V2 service override for an environment, service, infrastructure or cluster in the connected account. Supply target references and override type, with structured variables, manifests, configuration files or YAML. Optionally provide an identifier and Git storage/commit settings. Returns the created override and governance results.
Create services through the Harness batch service endpoint in the connected account. Supply a list of service definitions with identifier, organization and project identifiers, name, description, tags, or YAML as applicable. Returns created service details, validity and governance results, and provider page metadata.
Create multiple services in the connected Harness account with partial success support. Returns both successfully created services and failed attempts with error details and totals. Failed individual items are valid batch results; inspect them before retrying to avoid recreating successful items.
Create a Harness template in the connected account scope. Supply template YAML and template metadata, with optional Git storage settings and stable-version selection. Returns the created template definition, version, scope, and Git details.
Delete a Harness environment by identifier in the connected account. Optionally specify its organization and project, supply if_match for conditional deletion, or set force_delete to bypass reference and usage checks.
Delete a Harness environment group by identifier in the connected account. Optionally select its organization and project or provide Git context and a merge commit message. Set force_delete to bypass reference and usage checks. Returns the deletion result and entity identifiers.
Delete a Harness environment service override in the connected account. Specify the environment and service identifiers and, where applicable, the organization and project containing the override.
Delete a Harness infrastructure by identifier within an environment in the connected account. Optionally specify its organization and project, or set force_delete to bypass reference and usage checks.
Delete a Harness pipeline input set by identifier in the specified organization, project, and pipeline of the connected account. Supports conditional deletion with if_match and Git-backed input set branch, file, and commit options.
Delete a Harness organization by its identifier in the connected account. Optionally supply the organization version in if_match for conditional deletion.
Delete a Harness pipeline by identifier in a specified organization and project of the connected account. Supports conditional deletion with if_match and Git-backed pipeline branch, file, and commit options.
Delete a Harness pipeline trigger by identifier in the specified organization, project, and target pipeline of the connected account. Optionally supply if_match for conditional deletion. Returns the provider's deletion result.
Delete a Harness project by identifier in the connected account. Optionally specify its organization and supply the project version in if_match for conditional deletion.
Delete a Harness service by identifier in the connected account. Optionally specify its organization and project, supply if_match for conditional deletion, or set force_delete to bypass reference and usage checks.
Delete a Harness service override by its identifier in the connected account. Supply organization and project identifiers when the override belongs to those scopes. Returns Harness's boolean deletion result.
Delete a particular version of an account-scoped Harness template by template identifier and version label. Optionally provide a change comment or force deletion. Returns confirmation after Harness responds with No Content.
Download an uploaded runtime input file from a Harness pipeline execution, selecting its upload step execution and file name.
Download a Harness pipeline input file from its storage file path. Returns a downloadable file reference containing the original file bytes.
Start a Harness pipeline execution with runtime input YAML in the selected organization and project. Supports Git branch selection, input sets, notes and asynchronous plan creation. Returns the created plan execution ID and initial execution details; does not wait for the pipeline to finish.
Start an execution of selected Harness pipeline stages in an organization and project, with optional runtime input YAML and expression values. Returns the created plan execution ID and initial execution details; does not wait for execution to finish.
Start a Harness pipeline execution by merging input set references, with optional stage selection and final runtime input YAML. Supports pipeline and input-set Git branches, execution notes and asynchronous plan creation. Returns the created plan execution and initial state without waiting for completion.
Get one page of artifact and manifest trigger event history based on build source type. Returns event payloads, processing outcomes, target execution summaries, and page metadata. Optionally filter by source type, pipeline, organization, project, or pipeline search term. Pass the returned cursor to retrieve the next page.
Get a Harness environment by identifier in the connected account, optionally specifying its organization, project, and deleted state. Returns its YAML definition, tags, timestamps, validity details, and governance results.
Get a Harness environment group by identifier in the connected account. Optionally select organization, project, deleted state, and Git branch or Old Git Sync repository. Returns the group YAML, linked environments, timestamps, validity, and governance evaluation details.
Fetch a Harness pipeline execution's summary and execution graph by plan execution ID. Optionally select a stage run or render graphs for all stages and steps.
Fetch the full content of a specific annotation on a Harness pipeline execution using its plan execution ID and annotation context ID.
Fetch annotations for a specific Harness pipeline execution, including annotation summaries, styles, priorities, context IDs, and timestamps.
Fetch a Harness pipeline execution graph by plan execution ID within an organization and project. Returns its root node, nodes, adjacency lists, and execution metadata.
Retrieve the runtime input set YAML used by a pipeline execution, including its template YAML, input set details, branch, and resolved YAML when available. Optionally select whether and which expressions Harness should resolve.
Retrieve metadata for an existing Harness pipeline execution by its plan execution ID, including execution YAML with runtime inputs and templates resolved.
Retrieve notes for an existing Harness pipeline execution by its plan execution ID.
Get one page of governance policy evaluations for a Harness pipeline execution, including policy-set results, policy denial messages, and pagination metadata.
Retrieve retry history for a Harness pipeline execution, including attempt IDs, timestamps, statuses, run sequences, and retried or skipped stages. Requires the execution ID, pipeline identifier, organization, and project.
Fetch the Harness pipeline execution subgraph for a retried step-group node execution ID within a plan execution, organization, and project. Returns graph nodes, adjacency lists, and execution metadata.
Retrieve the Harness UI URL for an existing pipeline execution using its plan execution ID, pipeline identifier, organization, and project. This does not start or modify an execution.
Fetch a Harness pipeline execution's workflow graph for visualization by plan execution ID. Optionally start traversal at a node execution ID and limit the traversal depth. Returns graph data and node relationships.
Retrieve available Helm command names for a Harness service specification type, optionally filtered by Helm version, manifest store type, and step type.
Get a Harness infrastructure definition by its identifier and environment in the connected account. Optionally specify organization, project, and deleted state. Returns its YAML, provider and deployment types, service discovery status, timestamps, validity details, and governance results when available.
Fetch a Harness pipeline input set by identifier within an organization, project, and pipeline. Returns its YAML, tags, Git validity and input set error details. Supports Git branch/repository selection and optional cache loading.
Retrieve multiple input sets by identifier for a Harness pipeline. Only non-deleted input sets are returned, with tags, module and validity/error details. This is a read-only lookup.
Retrieve available Kubernetes command options for a Harness service specification type, optionally filtered by deployment step type.
Retrieve the available Kustomize command options for Harness services, such as Build.
Get a Harness organization by identifier in the connected account, including its name, description, tags, timestamps, and Harness-managed status.
Fetch a Harness overlay input set by identifier within an organization, project, and pipeline. Returns YAML, input set references, tags, and validity details. Supports Git branch/repository selection and optional cache loading.
Fetch a Harness pipeline by identifier within an organization and project. Returns pipeline YAML, optional template-resolved YAML, and validation, Git, governance, and storage metadata. Supports Git branch and Old Git Sync context.
Fetch a Harness pipeline summary by identifier within an organization and project. Returns stage and module information, execution history summary, and Git, validity, and storage details. Supports Git branch selection.
Retrieve one Harness pipeline trigger by its identifier, organization, project, and target pipeline. Returns its YAML definition, enabled state, validation errors, stage selection, webhook URL, and executor identity when available.
Retrieve the available Harness pipeline trigger categories and their supported trigger types for the connected account. Returns the complete catalog, not configured trigger instances; use List Pipeline Triggers for those.
Fetch a Harness pipeline trigger's detailed health, polling and webhook registration status, latest execution, YAML definition, and executor identity. Requires the trigger identifier and its organization, project, and target pipeline identifiers.
Get a Harness project by identifier in the connected account, optionally specifying its organization. Returns project details, enabled modules, tags, timestamps, and favorite status.
Get processing and execution details for a Harness webhook event while its trigger is queued and has not yet triggered the pipeline. Supply the webhook event ID.
Fetch a Harness pipeline's runtime input template YAML, expressions requiring replacement, and entity input metadata. Optionally select stages and service Git branches. Does not execute the pipeline or save an input set.
Get a Harness service by identifier in the connected account, optionally specifying its organization, project, and deleted state. Returns its YAML definition, deployment type, tags, timestamps, validity, and governance results.
Retrieve a Harness service override by its identifier in the connected account, optionally scoped to an organization and project. Returns its environment, service, infrastructure or cluster target, structured configuration, YAML and governance results.
Retrieve available runtime languages and serverless versions for Harness service plugins.
Retrieve the stable version of a Harness template at account scope, including template YAML and Git details. Optionally include input YAML and select a Git branch or remote parent entity context.
Retrieve the input schema for a version of an account-scoped Harness template, including input types, validation rules, field properties, and runtime or fixed-value dependencies.
Retrieve a particular version of an account-scoped Harness template, including its YAML, version metadata, Git details, and optional input YAML.
Get one page of Harness trigger history for an event correlation ID, including original payload, headers, processing outcomes, and pagination details.
Get one page of Harness trigger history correlated by event correlation ID. Uses the V2 response: event records include original payload, headers, final processing status and targetExecutionSummary (execution ID, run sequence, execution status, runtime inputs and start timestamp), rather than only trigger event metadata. Does not start an execution.
Get one page of event history for a Harness pipeline trigger, including processing outcomes and target execution summaries. Optionally request event payloads, search pipelines, and specify sorting.
Get all polled responses for a Harness pipeline trigger, including polled keys, polling document ID, and perpetual polling task state and delegate details.
Get Harness webhook event processing and pipeline execution details by event ID. Returns whether the event was found, processing status, payload, runtime inputs, warnings, execution details and execution URL when available.
Retrieve Harness webhook event processing details by event ID, including whether the event was found, its processing status, associated trigger and pipeline execution, original payload, runtime inputs, and warnings.
Import and create a Harness environment from a YAML file in a Git repository. Supply the repository, branch, and file path, with the target organization/project scope and Git connector when applicable. Returns the imported environment identifier and governance evaluation details.
Import and create a Harness infrastructure definition from a YAML file in a Git repository. Supply the target environment, repository, branch, and file path, plus organization, project, and Git connector when applicable. Returns the imported infrastructure identifier and available governance evaluation results.
Import and create a Harness pipeline from a YAML file in a Git repository into a specified organization and project. Optionally supply a pipeline name, description, YAML version, or force-import setting. Returns the imported pipeline identifier and governance and public-access results.
Import a Harness service YAML from a Git repository in the connected account. Specify the repository, branch, and file path, with optional organization, project, service identifier, connector, and import flags. Returns the imported service identifier and governance evaluation results when available.
Import a Harness template from Git at the connected account scope. Provide the template identifier and optional Git source, force-import, and template metadata settings. Returns the imported identifier and version.
Issue an interrupt on a Harness pipeline execution in a project. Choose AbortAll to abort the execution or UserMarkedFailure to mark it as failed. Returns the issued interrupt details, rather than waiting for execution completion.
Apply an AbortAll or UserMarkedFailure interrupt to a specific running step or stage in a Harness pipeline execution. Returns the issued interrupt ID and type; this does not wait for execution to finish.
List accessible Harness environments, optionally filtered by organization, project, environment identifiers, environment group, search text, or environment type. Returns one requested page; the provider does not supply pagination metadata.
List one page of Harness environment groups at account, organization, or project scope. Filter by identifiers, tags, search text, saved filter, or Git branch and repository. Returns linked environment details and a continuation cursor.
List one page of service overrides for a Harness environment, optionally filtered by service. Returns override YAML, governance results, page metadata, and a continuation cursor.
List one page of environments in a Harness project, optionally filtered by identifiers or search text.
List one page of pipeline execution identifiers and statuses in a Harness project using entity and tag filters, optionally narrowed to a pipeline or Git branch.
List one page of Harness pipeline execution outlines by pipeline identifier or execution IDs, optionally filtered by status and queued time.
List one page of infrastructure definitions in a Harness environment. Filter by identifiers, deployment type, custom deployment template, search text, or service references. Returns YAML, discovery, validity and governance details with pagination metadata and a continuation cursor.
List one page of regular input set metadata across Harness pipelines in a project, excluding overlay input sets. Optionally filter by pipeline identifiers and search text. Omitting pipeline identifiers lists all accessible input sets subject to RBAC. Returns pagination details and a continuation cursor.
List one page of input sets for a Harness pipeline, optionally filtered by type, search text, and Git branch or repository. Returns validity/error details and a continuation cursor for the next page.
List one page of Harness organizations accessible to the connected account, optionally filtered by identifier or search text.
List one page of pipeline executions in a Harness project, optionally filtered by pipeline, status, search text, or current-user ownership.
List one page of API-managed triggers for a Harness pipeline, including trigger health, webhook details, YAML, and last execution details. Optionally filter or sort the results.
List one page of pipelines in a Harness project, optionally filtered by search text or Git branch.
List one page of Harness projects accessible to the connected account, optionally within an organization or filtered by module and search text.
List one page of accessible Harness projects, optionally filtering by multiple organizations, modules, favorites, identifiers, or search text. Use the returned cursor to continue with the same filters.
List one page of Harness service-access records in the connected account. Optionally filter by organization, project, service identifiers, search text, deployment type, GitOps state, or deployment template. Returns service definitions, timestamps, validity, and governance results. Use page and size for pagination; the provider does not return a continuation token or page totals.
Retrieve the actions available for service hooks for a Harness service specification type. Returns the complete list; this endpoint is not paginated.
List one page of services in a Harness project, optionally filtered by identifiers, deployment type, tags, storage, GitOps state, or search text.
List one page of account-scoped Harness templates, optionally filtered by template state, entity or child type, identifier, name, description, or search text.
List one page of trigger event history for a Harness pipeline, including event outcomes, messages, and trigger metadata. Optionally filter by trigger identifier, event statuses, or trigger type.
Merge Harness input set references into runtime input YAML for a pipeline, optionally selecting stages and adding final override YAML. Can include the complete merged pipeline YAML. Returns YAML and validation details without starting an execution or saving an input set; inspect errorResponse for merge errors.
Move a Harness environment's YAML configuration between inline storage and Git. Set move_config_type to INLINE_TO_REMOTE for Git storage or REMOTE_TO_INLINE to return to inline storage. Supply the environment's scope and relevant repository, connector, branch, file path, and commit options.
Move a Harness infrastructure's YAML configuration between inline storage and Git. Set move_config_type to INLINE_TO_REMOTE for Git storage or REMOTE_TO_INLINE to return to inline storage. Supply the infrastructure and environment identifiers, scope, and relevant repository, connector, branch, file path, and commit options.
Move a Harness service override YAML configuration from inline storage to a remote repository, or from remote storage to inline. Supply the override selectors, move direction and repository settings as applicable. Returns the successfully moved override's identifier and scope.
Move a Harness service's YAML configuration between inline storage and Git. Use move_config_type INLINE_TO_REMOTE to move to Git or REMOTE_TO_INLINE to return to inline storage. Supply the service scope and applicable Git connector, repository, branch, file path, and commit options.
Force-refresh the Git file cache for a remote Harness pipeline input set and return the freshly fetched YAML, identity, tags, and validity details. Requires an explicit Git branch (the repository default is not inferred) and the PIPE_GITX_FORCE_REFRESH feature flag enabled on the account.
Force-refresh the Git file cache for a remote Harness pipeline and return the freshly fetched pipeline YAML and validation, governance, and storage metadata. Use to recover from stale Git-to-Harness sync. Requires an explicit Git branch (the repository default is not inferred) and the PIPE_GITX_FORCE_REFRESH feature flag enabled on the account.
Recursively refresh and update all template inputs in a Harness pipeline. Supply the pipeline identifier and its organization/project scope, and Git location and concurrency fields when updating a Git-synced pipeline. Returns the provider's boolean refresh result.
Resume a manual execution node or mark it as failed in a Harness pipeline execution. Requires the node execution ID and its organization and project. Returns the request result without waiting for the pipeline to finish.
Retry a previously executed Harness pipeline from selected stages in an organization and project. Provide the previous execution ID and stage identifiers; optionally retry only failed stages in a parallel group. Returns the created execution ID and initial details without waiting for completion.
Retry a previous Harness pipeline execution from selected stages with optional runtime input YAML and expression values. Supports failed parallel-group stage selection, execution notes and asynchronous plan creation. Returns the new execution ID and initial details without waiting for completion.
Trigger a Harness service rollback using its instance key and infrastructure mapping identifier. Optionally specify organization and project scope. Returns whether rollback was triggered, a result message, and the rollback plan execution ID when available; inspect rollbackTriggered for the outcome.
Trigger a Harness service rollback in a specific environment, optionally selecting infrastructure, artifact, and chart version. Returns whether the rollback was triggered and its pipeline execution ID when available; triggering does not mean the rollback has completed.
Trigger rollback for multiple service and environment targets in the connected Harness account, using the latest pipeline execution group per target. Returns individual target outcomes and triggered/failed totals. A target failure does not fail the entire batch; inspect rollbackTriggered and message for each result.
Mark an existing Harness template version as stable at account scope. Optionally specify a Git branch, remote parent template context, and a comment.
Update an existing Harness environment's definition, type, name, tags, or YAML at account, organization, or project scope. Supply the identifier and scope of the existing environment.
Update the Git metadata of an existing remote Harness environment and return its identifier. Supply the environment's scope and the connector reference, repository name, or file path to update.
Update an existing Harness environment group by identifier using its YAML definition. Optionally supply organization, project, color, conditional-update entity tag, and Git update selectors. For Git updates, provide last_object_id from the entity GET response. Returns the updated group and linked environments.
Update the notes for a Harness pipeline execution in a project.
Update an existing Harness infrastructure definition by identifier using its complete YAML specification. Optional fields supply organization, project, environment reference, display details, tags, provider type, and service discovery settings. Returns the updated infrastructure with available validity, discovery, and governance evaluation results.
Update Git metadata for an existing remote Harness infrastructure in an environment. Optionally supply organization, project, Git connector, repository name, and definition file path. Returns the updated infrastructure identifier when supplied by Harness.
Update an existing Harness pipeline input set using its complete replacement YAML definition. Specify its organization, project, pipeline, and input set identifier. Supports Git branch, commit, and entity-version controls. Returns the saved input set and validity details.
Update Git metadata for an existing remote Harness pipeline input set. Specify its organization, project, pipeline, and input set identifier, with optional connector reference, repository name, and file path. Returns the updated input set identifier when supplied by Harness.
Update settings of an existing Harness organization in the connected account. Optionally supply If-Match to check the organization version.
Update an existing Harness pipeline overlay input set with its complete replacement YAML definition. Specify the organization, project, pipeline, and overlay input set identifier. Supports Git branch, commit, and entity-version controls. Returns the saved overlay and validity details.
Update a Harness pipeline by identifier using its complete YAML definition. Supports Git-synced updates, optimistic concurrency, dynamic executions, and public access settings.
Update Git metadata for a remote Harness pipeline in the specified organization and project. Optionally set its connector reference, repository name, and file path. Returns the identifier of the updated pipeline.
Update an existing Harness pipeline trigger from replacement YAML in an organization and project, optionally setting its executor identity and a conditional entity tag. Returns saved trigger details and any validation errors.
Update an existing Harness pipeline trigger with a complete replacement YAML definition in an organization and project. Supports a conditional entity tag and returns saved trigger details and validation diagnostics. To supply an executor identity separately, use Update Pipeline Trigger.
Update a Harness project's details, including its name, description, color, enabled modules, and tags. Optionally supply the project version in if_match for optimistic concurrency control.
Update an existing Harness service's name, description, tags, or YAML at account, organization, or project scope. Supply the existing service identifier and scope in the fields or YAML. Git-backed updates support branch, file, connector, commit, and conflict-resolution options; obtain last_object_id from GET.
Update the Git metadata of an existing remote Harness service and return its identifier. Supply the service's organization and project identifiers and the connector reference, repository name, or file path to update.
Update a Harness service override in the connected account using its environment reference and override type, optionally specifying its identifier, organization, project, service, infrastructure or cluster. Supply structured configuration or YAML; returns the updated override and governance evaluation details.
Update the Git connector, repository name or file path of an existing remote Harness service override. Select the override by identifier or its environment, service, infrastructure and override type in the appropriate organization and project. Returns the updated override identifier and scope references.
Update Git repository, file path, and connector metadata for an account-scoped Harness template across multiple versions. Supply one entry per version in updates.
Update an existing template version at account scope, including YAML, metadata, and optional Git settings.
Create or update a Harness environment by identifier at account, organization, or project scope. Supply its Production or PreProduction type and optional name, description, tags, color, or YAML definition. Returns the saved environment with validity and governance results when available.
Create or update a service override for a Harness environment in the connected account. Supply organization, project, environment and service identifiers and the override YAML as applicable. Returns the stored override and governance evaluation results when available.
Create or update a Harness service by identifier at account, organization, or project scope. Supply the service identifier and scope in the fields or service YAML, with optional name, description, tags, and If-Match entity tag.
Validate template inputs in a stored Harness pipeline's YAML specification. Returns whether the YAML is valid and a nested error summary with referenced template details when inputs are invalid. Optionally select a Git branch and repository.
The Harness integration connects your Dench AI CRM directly to Harness, so agents can read and act on your Harness data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
150 actions are available for agents to invoke on your behalf. Every call runs through Harness's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Harness and click Connect — you'll authorize access through Harness's own sign-in flow. No API keys or code required.
Ask an agent to use Harness in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Harness integration connects your AI CRM to Harness, so AI agents can work with your Harness data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Harness integration currently exposes 150 actions, including Add Approval Activity, Add Execution Tags, Check Environment Allowed Values, Check Execution Retry, Check Rollback Eligibility, and Check Service Allowed Values. Agents invoke them on your behalf from chat or from automations.
No. You connect Harness from your Dench workspace using Harness's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Harness's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Harness connection from your workspace settings at any time.