> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/3.0/in-harness-3.0/connectors/types.md).

# Connector Types

Harness 3.0 supports a wide range of connector types organized into categories. Each category serves a specific integration purpose within the platform, and each type exposes its own set of configuration properties. Use this reference to identify the connector you need and the properties you must supply before you configure it.

***

### What will you learn in this topic? <a href="#what-will-you-learn-in-this-topic" id="what-will-you-learn-in-this-topic"></a>

By the end of this topic, you will be able to:

* [Select a source control connector and configure its connection and authentication properties](#code-repositories).
* [Identify the registry and build server connectors available for artifact retrieval](#artifact-repositories).
* [Choose the correct credential type for each cloud platform](#cloud-providers).
* [Integrate an external vault or key management service](#secret-managers).
* [Connect Kubernetes and Rancher deployment targets](#infrastructure).
* [Connect observability platforms for deployment verification and rollback](#monitoring-and-observability).

***

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

Before you select a connector type, ensure you have the following:

* **Connectors overview**: Familiarity with connector scope and connection types. For more information on the connector model, see [Connectors overview](/harness-platform/3.0/in-harness-3.0/connectors.md).
* **Provider account access**: An account on the external service with permission to create tokens, keys, or service accounts.
* **Delegate availability**: A [Harness Delegate](/harness-platform/3.0/harness-platform-resources/delegates/delegate-closed-beta/delegate-overview.md) with network access to the provider, for services hosted in a private network.

***

### Code repositories <a href="#code-repositories" id="code-repositories"></a>

Code repository connectors provide access to source code, manifests, and configuration files stored in version control systems. You can use these connectors during the CI build stage and to fetch Kubernetes manifests, Helm charts, and Terraform modules.

**Use cases:** CI/CD pipeline codebase configuration for build triggers, fetching Kubernetes manifests and Helm value files, Terraform module sources and remote state configuration, and webhook-based triggers that run pipelines automatically on push or pull request events.

**Supported platforms:** GitHub, GitLab, Bitbucket, Azure Repos, Generic Git

**Common configuration**

| Property        | Description                                               |
| --------------- | --------------------------------------------------------- |
| Connection type | HTTP or SSH.                                              |
| URL             | Repository or account-level URL.                          |
| Authentication  | Personal access token, OAuth, SSH key, or GitHub App.     |
| API access      | Enable API access for webhook triggers and status checks. |

***

### Artifact repositories <a href="#artifact-repositories" id="artifact-repositories"></a>

Artifact repository connectors integrate with registries and build servers to retrieve container images, Helm charts, and binary packages for deployment.

**Use cases:** Pulling container images for Kubernetes deployments, fetching Helm charts from chart museums or OCI registries, retrieving build artifacts from CI servers such as Jenkins or Bamboo, and artifact version selection for deployment and rollback.

**Supported platforms:** Docker Registry, Artifactory (JFrog), Nexus, Helm Chart Repository, Azure Artifacts, Bamboo, Jenkins

**Common configuration**

| Property       | Description                                            |
| -------------- | ------------------------------------------------------ |
| Registry URL   | The base URL of the artifact registry or build server. |
| Authentication | Username and password, token, or anonymous access.     |
| Provider type  | Docker Hub, ECR, GCR, ACR, or a custom registry.       |

***

### Cloud providers <a href="#cloud-providers" id="cloud-providers"></a>

Cloud provider connectors authenticate and interact with major cloud platforms for infrastructure provisioning, deployment, and resource management.

**Use cases:** Infrastructure provisioning with Terraform, CloudFormation, or ARM templates; ECS, EKS, GKE, and AKS cluster deployments; Lambda, Cloud Functions, and Azure Functions serverless deployments; and cloud resource tagging, compliance checks, and cost management.

**Supported platforms:** AWS, Google Cloud Platform (GCP), Microsoft Azure, Terraform Cloud, VMware Tanzu, Spot, Physical Data Center, Salesforce

**Common configuration**

| Property                      | Description                                                                                                                                                          |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Credential type               | Identity and Access Management (IAM) role, service account key, service principal, access key and secret, or delegate-based credentials inherited from the delegate. |
| Region / zone                 | Target region or zone for resource operations.                                                                                                                       |
| Cross-account / cross-project | Security Token Service (STS) assume-role ARN for AWS, project ID for GCP, or subscription and tenant ID for Azure.                                                   |
| Delegate selectors            | Target specific delegates for on-premise or private network access.                                                                                                  |

***

### Secret managers <a href="#secret-managers" id="secret-managers"></a>

Secret manager connectors integrate with external vaults and key management services to store and retrieve sensitive data such as passwords, tokens, certificates, and encryption keys.

**Use cases:** Centralizing secrets storage across all Harness connectors and pipelines, meeting compliance requirements for external secret storage such as SOC 2 and HIPAA, rotating credentials without modifying connector or pipeline configurations, and encrypting sensitive data at rest using Key Management Service (KMS) backed encryption keys.

**Supported platforms:** AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, Azure Key Vault, AWS KMS, GCP KMS, Custom Secret Manager

**Common configuration**

| Property             | Description                                                                |
| -------------------- | -------------------------------------------------------------------------- |
| Vault URL / endpoint | Base URL of the secret manager service.                                    |
| Authentication       | Token, AppRole, IAM, service account, or certificate-based authentication. |
| Secret engine / path | The path prefix or engine name for secret storage.                         |
| Default              | Whether this is the default secret manager for the scope.                  |

Every Harness account includes a built-in secret manager, [Harness Secret Manager](/harness-platform/3.0/harness-platform-resources/secrets/secrets-management/harness-secret-manager-overview.md), that uses Google KMS for encryption. You can configure an external secret manager as the default for any scope (**Account**, **Organization**, or **Project**). All new secrets created at that scope then use the external manager automatically.

***

### Infrastructure <a href="#infrastructure" id="infrastructure"></a>

Infrastructure connectors provide access to container orchestration platforms and cluster management systems that act as deployment targets.

**Use cases:** Kubernetes rolling deployments, canary releases, and blue/green deployments; Helm chart installations and upgrades across multiple clusters; and multi-cluster management with Rancher for fleet-wide deployments.

**Supported platforms:** Kubernetes, Rancher

**Common configuration**

| Property       | Description                                                                                          |
| -------------- | ---------------------------------------------------------------------------------------------------- |
| Cluster URL    | The Kubernetes API server endpoint or Rancher management server URL.                                 |
| Authentication | Service account token, client certificate, OpenID Connect (OIDC), or delegate-inherited credentials. |
| Namespace      | Default namespace for deployment operations (optional).                                              |

***

### Monitoring and observability <a href="#monitoring-and-observability" id="monitoring-and-observability"></a>

Monitoring connectors integrate with observability platforms for deployment verification, health checks, and automated rollback decisions based on real-time metrics and logs.

**Use cases:** Continuous Verification (CV) during canary and rolling deployments, automated rollback based on error rate, latency, or custom metric thresholds, incident alerting and on-call notification through PagerDuty and OpsGenie, and log analysis for deployment health assessment and anomaly detection.

**Supported platforms:** Datadog, Splunk, Dynatrace, Elastic (ELK), New Relic, AppDynamics, Prometheus, PagerDuty, SumoLogic, OpsGenie, Error Tracking, Custom Health Source

**Common configuration**

| Property                 | Description                                                                   |
| ------------------------ | ----------------------------------------------------------------------------- |
| API endpoint             | The monitoring platform's API URL or data ingestion endpoint.                 |
| API key / token          | Authentication credential stored as a Harness secret.                         |
| Application / service ID | Provider-specific identifiers that target the correct application or service. |

***

### Ticketing systems <a href="#ticketing-systems" id="ticketing-systems"></a>

Ticketing connectors integrate with issue tracking and IT Service Management (ITSM) platforms for change management, approval workflows, and deployment tracking.

**Use cases:** Creating and updating Jira tickets as part of deployment pipelines, ServiceNow change request approvals as pipeline gates, and automated deployment tracking and audit trails in ticketing systems.

**Supported platforms:** Jira, ServiceNow

**Common configuration**

| Property        | Description                                                               |
| --------------- | ------------------------------------------------------------------------- |
| Instance URL    | The Jira Cloud or Jira Server URL, or the ServiceNow instance URL.        |
| Authentication  | Username and API token for Jira, or username and password for ServiceNow. |
| Project / table | Default project key for Jira, or table name for ServiceNow.               |

***

### Communication <a href="#communication" id="communication"></a>

Communication connectors integrate with messaging and collaboration platforms to send notifications about pipeline events, approval requests, and deployment status.

**Use cases:** Pipeline success and failure notifications to team channels, approval request notifications with actionable buttons, and deployment status updates and release announcements.

**Supported platforms:** Slack, Microsoft Teams, Zoom

**Common configuration**

| Property    | Description                                                                             |
| ----------- | --------------------------------------------------------------------------------------- |
| Webhook URL | Incoming webhook URL for the target channel or team.                                    |
| Bot token   | OAuth bot token for Slack API access. This is optional and enables richer integrations. |

***

### Other connectors <a href="#other-connectors" id="other-connectors"></a>

Additional connector types serve specialized integration needs within the Harness platform.

#### Database (JDBC) <a href="#database-jdbc" id="database-jdbc"></a>

Java Database Connectivity (JDBC) connectors enable direct database connectivity for data validation steps, database migration scripts, and custom verification queries during deployments. JDBC connectors support MySQL, PostgreSQL, Oracle, SQL Server, and other JDBC-compatible databases.

#### Documentation (Confluence) <a href="#documentation-confluence" id="documentation-confluence"></a>

Confluence connectors allow pipelines to read from or publish to Confluence pages, which enables automated documentation updates as part of the release process.

#### MCP (GitHub MCP) <a href="#mcp-github-mcp" id="mcp-github-mcp"></a>

The GitHub [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) connector enables the Harness AI assistant (AIDA) to interact with GitHub repositories, issues, and pull requests through a structured tool interface for AI-driven development workflows.

***

### Next steps <a href="#next-steps" id="next-steps"></a>

* [Manage connectors](/harness-platform/3.0/in-harness-3.0/connectors/manage.md): To create, test, and maintain connectors at the correct scope.
* [Connector configuration reference](/harness-platform/3.0/in-harness-3.0/connectors/configure.md): To copy YAML, Terraform, and REST API examples for each connector type.
* [Connector troubleshooting](/harness-platform/3.0/in-harness-3.0/connectors/troubleshooting.md): To diagnose authentication, network, and permission failures.