Skip to main content

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

Network & credentials

Clear the firewall path; know every credential pattern.

Warehouse connectors

Snowflake, BigQuery, Redshift, Databricks, PostgreSQL — production-grade.

Private networks

SSH tunnels through a bastion for databases with no public endpoint.

BI tools

Tableau and Power BI — including the sync step everyone misses.

Files, Drive & APIs

Zero-setup files, service-account Sheets, secure API access.

Validate & operate

The five-question smoke test, rotation, resync, decommission.

​
How to use this workshop

  1. You need the connector:write permission (members have it by default unless your admin tightened it).
  2. Do Modules 0–1 always — they prevent the failure modes behind most connector tickets.
  3. Jump to the module for your source type; each warehouse section is self-contained.
  4. Finish with Module 6 regardless of path — the smoke test is the difference between “test passed” and “actually works.”
Setup steps follow current product docs at docs.textql.com. SaaS deployment assumed; VPC / on-prem deployments skip IP whitelisting and confirm network requirements with their TextQL representative.

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.