> For the complete documentation index, see [llms.txt](https://docs.algenta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algenta.ai/connectors.md). # Connectors - [Connectors overview](https://docs.algenta.ai/connectors/overview.md): Connectors are configured, testable connections to your external data — databases, warehouses, object storage, REST APIs, and files — that back a governed source the engine can query. - [Connect a database](https://docs.algenta.ai/connectors/databases.md): Connect a database directly to Algenta — the engine reads your tables under a governed contract, never copies them, and keeps credentials encrypted at rest. - [Connectors reference](https://docs.algenta.ai/connectors/reference.md): Every supported Algenta connector type, grouped by category, with its required and optional config fields, the canonical type names, and the untested-live-error status lifecycle. - [Snowflake](https://docs.algenta.ai/connectors/snowflake.md): Create a Snowflake connector with its real config fields, test the connection, browse its tables, onboard one as a dataset, and run a governed query against it. - [BigQuery](https://docs.algenta.ai/connectors/bigquery.md): Connect Google BigQuery to Algenta — create a bigquery connector with project and service-account credentials, test it, browse datasets, and run a governed query. - [ClickHouse](https://docs.algenta.ai/connectors/clickhouse.md): Connect ClickHouse to Algenta as a governed connector. Configure host, port, database, user, password, and secure, then test, browse, connect, and query. - [PostgreSQL](https://docs.algenta.ai/connectors/postgres.md): Create a PostgreSQL connector with its real config fields, test the connection, browse its tables, onboard one as a governed dataset, and run a first governed query against it. - [Oracle Database](https://docs.algenta.ai/connectors/oracle.md): Connect Oracle Database or Autonomous Database with Algenta's bundled Thin-mode driver, verify credentials once, browse schemas, and onboard a table or query. - [MySQL](https://docs.algenta.ai/connectors/mysql.md): Create a MySQL connector with its real config fields, and understand the managed connection-test behavior for MySQL before you onboard data. - [Microsoft SQL Server](https://docs.algenta.ai/connectors/mssql.md): Create a Microsoft SQL Server connector with its real config fields, and understand the managed connection-test behavior for SQL Server before you onboard data. - [SQLite](https://docs.algenta.ai/connectors/sqlite.md): Create a SQLite connector from a database file path, test the connection, browse its tables, onboard one as a governed dataset, and run a first governed query against it. - [Amazon Redshift](https://docs.algenta.ai/connectors/redshift.md): Create an Amazon Redshift connector with its real config fields, test the connection over the PostgreSQL wire, browse its tables, onboard one as a governed dataset, and run a first governed query. - [Amazon S3](https://docs.algenta.ai/connectors/s3.md): Create an Amazon S3 connector with its real config fields, test object access, browse a bucket, onboard one object as a governed dataset, and run a first governed query against it. - [Google Cloud Storage](https://docs.algenta.ai/connectors/gcs.md): Create a Google Cloud Storage connector with its real config fields, test object access, browse a bucket, onboard one object as a governed dataset, and run a first governed query. - [Azure Blob Storage](https://docs.algenta.ai/connectors/azure-blob.md): Create an Azure Blob Storage connector with its real config fields, test blob access, browse a container, onboard one blob as a governed dataset, and run a first governed query. - [Redis](https://docs.algenta.ai/connectors/redis.md): Create a Redis connector with its real config fields, test the connection, browse its keys, onboard selected keys as a dataset, and run a governed query against them. - [Neo4j](https://docs.algenta.ai/connectors/neo4j.md): Create a Neo4j connector with its real config fields, test the connection, browse its labels and relationship types, onboard a selection as a dataset, and run a governed query against it. - [Elasticsearch](https://docs.algenta.ai/connectors/elasticsearch.md): Create an Elasticsearch connector with its real config fields, test the connection, browse its indices, onboard one as a dataset, and run a governed query against it. - [Files & uploads](https://docs.algenta.ai/connectors/files.md): Create a file connector for CSV, TSV, JSON, Excel, or Parquet data with its real config fields, test that it parses, onboard it as a dataset, and run a governed query against it. - [Code repositories](https://docs.algenta.ai/connectors/code-repositories.md): Create a repository connector for GitHub, GitLab, Bitbucket, a local checkout, or an archive, test that the source is reachable, and browse its files to feed repository intelligence. - [REST API](https://docs.algenta.ai/connectors/rest-api.md): Create a rest connector for any HTTP JSON API — set base\_url and auth\_type, test reachability, browse endpoints, connect a dataset, and run a governed query against it. --- # 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.algenta.ai/connectors.md?ask=&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.