CloudQuery Platform
  • Introduction
    • Welcome to CloudQuery Platform
    • Getting Help
  • Quickstart
    • Creating a New Account
    • Platform Activation
  • Core Concepts
    • Integrations
    • Syncs
    • Filters & Queries
    • SQL Console
    • Reports
  • Integration Guides
    • Setting up an AWS Integration
    • Setting up a GCP Integration
    • Setting up an Azure Integration
    • Setting up a GitHub Integration
    • Setting up a K8s Integration
      • Using AWS EKS
      • Using Azure AKS
      • Using GCP GKE
    • General Integration Setup Guide
    • General Destination Setup Guide
  • Syncs
    • Setting up a Sync
    • Monitoring Sync Status
  • Cloud insights
    • From cloud asset inventory to insights
      • Security-focused queries
      • Compliance-focused queries
      • FinOps-focused queries
  • Production Deployment
    • Enabling Single Sign-on (SSO)
      • Single Sign-On with Google
      • Single Sign-On with Microsoft
      • Single Sign-On with Okta
  • User Management
    • Platform Roles Overview
    • Workspace Roles Overview
  • Advanced Topics
    • Understanding Platform Views
    • Performance Tuning
  • Reference
    • Filter Query Syntax
  • API Reference
  • CLI Docs
  • CloudQuery Hub
Powered by GitBook
On this page

Was this helpful?

  1. Integration Guides

General Integration Setup Guide

PreviousUsing GCP GKENextGeneral Destination Setup Guide

Last updated 1 month ago

Was this helpful?

To set up a new integration, go to Data Pipelines → Integrations and click Create Integration:

Search for the name of your integration. In the example below, we searched for Microsoft Entra ID (Azure AD):

On the next screen, enter the Integration Name to identify the integration by later (if unsure, use the name of the Integration).

If applicable, fill out the Yaml specification. The link to the integration documentation will have more information about the format required.

Most of the integrations will require some form of authentication. We recommend using the Secrets section below to make the values available to the sync as environment variables. Reference the variables using placeholders such as ${my_secret_value} in the YAML configuration.

When you're ready to test, click Test Connection. If there are any errors during the test, they will be displayed on the page.

Next Steps

With your integration created, you can now proceed to use it in a . This will give you the opportunity to specify when your sync should be run, and to which destination databases.

new sync