> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Your Data

> A hands-on workshop for data engineers, platform admins, and technical leads: get every kind of data source connected to TextQL correctly the first time — warehouses, private-ne…

A hands-on workshop for **data engineers, platform admins, and technical leads**: get every kind of data source connected to TextQL correctly the first time — warehouses, private-network databases, BI tools, files, Google Drive, and external APIs — with credentials done right and a validation habit that catches problems before your users do.

Hands-on format: short modules, exact setup steps, copy-paste commands, checkpoints. **\~2.5 hours** end to end — but most teams run only the modules for sources they actually use.

## What you'll be able to do

<CardGroup cols={2}>
  <Card title="Network & credentials">Clear the firewall path; know every credential pattern.</Card>
  <Card title="Warehouse connectors">Snowflake, BigQuery, Redshift, Databricks, PostgreSQL — production-grade.</Card>
  <Card title="Private networks">SSH tunnels through a bastion for databases with no public endpoint.</Card>
  <Card title="BI tools">Tableau and Power BI — including the sync step everyone misses.</Card>
  <Card title="Files, Drive & APIs">Zero-setup files, service-account Sheets, secure API access.</Card>
  <Card title="Validate & operate">The six-question smoke test, rotation, resync, decommission.</Card>
</CardGroup>

## How to use this workshop

* You need the `connector:write` permission (members have it by default unless your admin tightened it).
* Do **Modules 0–1 always** — they prevent the failure modes behind most connector tickets.
* Jump to the module for **your** source type; each warehouse section is self-contained.
* Finish with **Module 6 regardless of path** — the smoke test is the difference between "test passed" and "actually works."

<Warning>
  Setup steps follow current product docs at [docs.textql.com](https://docs.textql.com/core/datasources/the-connectors-page). SaaS deployment assumed; **VPC / on-prem deployments skip IP whitelisting** and confirm network requirements with their TextQL representative.
</Warning>

<Accordion title="For facilitators — running this as a guided session">
  **T-minus-1-day pre-flight:** run the workshop's key prompts end-to-end in the session workspace — confirm logins, connectors, and the features this workshop touches are enabled for every attendee; have a fallback demo workspace ready in case a customer connector fails live. **Pacing:** when a long prompt is running (2–4 min), fire it first, then discuss the concept while Ana works — never watch a spinner in silence. If behind schedule, cut sections marked optional, never the checkpoints. **Group sessions:** attendees drive, you narrate; collect every miss or wrong answer in a shared doc — that list is the ontology backlog. With 10+ attendees on one warehouse, stagger the heavy prompts.
</Accordion>

<Note>
  **🤖 Prefer to have Ana run this workshop?** Open a thread with your data connected and paste the prompt below — Ana walks you through it on your own data, one step at a time. You run each prompt; she coaches. *(Air-gapped / VPC tenants where Ana can't reach the web: download [`ana-runner.md`](https://github.com/TextQLLabs/workshops/blob/main/connect-your-data/ana-runner.md) and paste its module list instead.)*
</Note>

```text Run with Ana theme={null}
Hey Ana — facilitate the "Connect Your Data" workshop with me on this workspace. It has steps I do in the console/CLI, so: first inspect the current state (connectors / roles / context / git, as relevant) and tell me where we're starting. Then go ONE step at a time — for analysis steps hand me the prompt to run; for console/setup steps tell me exactly what to do, then WAIT until I say "done" and re-check before moving on. If I leave and come back, re-inspect and resume. Start by telling me what you see.
```

[**▶ Open in Ana — prompt loaded**](https://app.textql.com/chat/new?prefill=Hey%20Ana%20%E2%80%94%20facilitate%20the%20%22Connect%20Your%20Data%22%20workshop%20with%20me%20on%20this%20workspace.%20It%20has%20steps%20I%20do%20in%20the%20console/CLI%2C%20so%3A%20first%20inspect%20the%20current%20state%20%28connectors%20/%20roles%20/%20context%20/%20git%2C%20as%20relevant%29%20and%20tell%20me%20where%20we%27re%20starting.%20Then%20go%20ONE%20step%20at%20a%20time%20%E2%80%94%20for%20analysis%20steps%20hand%20me%20the%20prompt%20to%20run%3B%20for%20console/setup%20steps%20tell%20me%20exactly%20what%20to%20do%2C%20then%20WAIT%20until%20I%20say%20%22done%22%20and%20re-check%20before%20moving%20on.%20If%20I%20leave%20and%20come%20back%2C%20re-inspect%20and%20resume.%20Start%20by%20telling%20me%20what%20you%20see.)

Ana gates on the setup steps and resumes if you step away. (Air-gapped / VPC tenants: download [ana-runner.md](https://github.com/TextQLLabs/workshops/blob/main/connect-your-data/ana-runner.md) and follow the steps.)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.