> ## 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...

<p>A hands-on workshop for <b>data engineers, platform admins, and technical leads</b>: 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.</p>
<p>Hands-on format: short modules, exact setup steps, copy-paste commands, checkpoints. <b>\~2.5 hours</b> end to end — but most teams run only the modules for sources they actually use.</p>

## 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 five-question smoke test, rotation, resync, decommission.</Card>
</CardGroup>

## How to use this workshop

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

<Warning>
  Setup steps follow current product docs at <a href="https://docs.textql.com/core/datasources/the-connectors-page" target="_blank">docs.textql.com</a>. SaaS deployment assumed; <b>VPC / on-prem deployments skip IP whitelisting</b> and confirm network requirements with their TextQL representative.
</Warning>

<Accordion title="For facilitators — running this as a guided session">
  <p><b>T-minus-1-day pre-flight:</b> 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. <b>Pacing:</b> 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. <b>Group sessions:</b> 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.</p>
</Accordion>