Skip to main content
The Integrations Service provides programmatic access to third-party service integrations configured in Kubiya, enabling agents to interact with external systems like GitHub, Slack, AWS, and more.
Use the Integrations Service whenever you need to understand which external systems are connected to Kubiya, verify that required integrations are ready before running workflows, or retrieve credentials just-in-time so agents can call out to third-party APIs safely.

Overview

Integrations in Kubiya connect the platform to external services and APIs. The Integrations Service allows you to:
  • List Integrations: View all configured integrations and their connection status
  • Get Integration Details: Access specific integration configurations and metadata
  • Retrieve Credentials: Securely access integration credentials for API calls
From the SDK you typically use these operations to build health dashboards, pre-flight checks for critical vendors (GitHub, Slack, AWS, etc.), and helper utilities that fetch and clean up credentials around specific API calls.
Integration configuration (adding, updating, deleting integrations) is performed through the Kubiya Dashboard. The SDK provides read-only access to integration information.

Quick Start

Core Concepts

Integration Types

Kubiya supports various integration categories:
  • Version Control: GitHub, GitLab, Bitbucket
  • Communication: Slack, Microsoft Teams, Discord
  • Cloud Providers: AWS, Azure, GCP
  • Monitoring: Datadog, New Relic, PagerDuty
  • Ticketing: Jira, ServiceNow, Linear
  • CI/CD: Jenkins, CircleCI, GitHub Actions
  • Databases: PostgreSQL, MySQL, MongoDB

Integration States

  • Connected: Integration is configured and credentials are valid
  • Disconnected: Integration is configured but credentials are invalid or expired
  • Not Configured: Integration type is available but not set up

Special Integrations

Some integrations (Jira, GitHub App) have special handling:
  • Always use integration ID "0"
  • Managed differently by the platform
  • May have organization-wide configuration

Basic Usage

List All Integrations

List Connected Integrations Only

Get Integration Details

Get Integration Credentials

Credentials contain sensitive authentication data. Always handle them securely and clear from memory after use.

Get Special Integration Credentials

Special integrations (Jira, GitHub App) always use ID "0" internally, regardless of the ID you provide. This is handled automatically by the SDK.

Practical Examples

The following examples show how to use the Integrations Service for real-world scenarios, such as listing integrations, retrieving credentials, and handling integration states. Each example includes a short explanation of when and why you might use it.

1. Integration Health Dashboard

Use this pattern to build a simple dashboard or scheduled job that reports which integrations are connected, disconnected, or stale so you can react before they break workflows. Monitor all integrations and report connection status:

2. Integration Configuration Validator

Use this validator as a pre-flight check to ensure that all vendors your agents depend on are configured and connected before deploying environments or running scheduled jobs. Validate required integrations are configured and connected:

3. Integration Credentials Manager

Use this context manager whenever you need to work with raw integration credentials so you load them only for the duration of an operation and then clear them from memory. Safely retrieve and use integration credentials:

4. Multi-Integration Query

Use this helper to fan out read-only queries across multiple integrations in parallel, for example to build aggregated views across GitHub, AWS, and Slack. Query data from multiple integrations simultaneously:

5. Integration Usage Analytics

Use this analytics helper to understand which vendors and integration types are most common in your organization and how broadly integrations are connected. Analyze integration usage patterns:

Error Handling

Integration operations can fail if an integration is missing, disconnected, misconfigured, or if credentials cannot be fetched due to permission or network issues. The following patterns show how to catch IntegrationError along with common SDK errors, and how to distinguish not-found and permission problems when accessing credentials.

Best Practices

These patterns help you treat integrations as a reliable, observable dependency: always verify connectivity, avoid unnecessary API calls, handle special vendor behavior, and monitor health for critical systems.

1. Check Integration Connection Before Use

Always verify that an integration is connected before relying on it in a workflow, so failures are caught early rather than surfacing as opaque API errors.

2. Cache Integration List for Performance

Cache the integration list when you need to query it frequently (for dashboards or schedulers) so you reduce API calls while still refreshing periodically.

3. Handle Special Integrations

Some vendors (like Jira and GitHub App) have special handling around IDs; centralizing that logic makes your code easier to reason about and less error-prone.

4. Monitor Integration Health

Set up lightweight, recurring checks for your most critical integrations so you can alert quickly when something becomes disconnected.

API Reference

Methods

Integration Object Structure

Supported Integration Vendors

Common integration vendors include:
  • Version Control: github, gitlab, bitbucket
  • Communication: slack, teams, discord
  • Cloud: aws, azure, gcp
  • Monitoring: datadog, newrelic, pagerduty
  • Ticketing: jira, servicenow, linear
  • CI/CD: jenkins, circleci, github_actions

Next Steps

Secrets Service

Manage secrets and credentials

Context Graph

Query the knowledge graph

Error Handling

Handle SDK exceptions

Best Practices

SDK best practices guide