Embed TextQL in Your Product

A workshop of short, hands-on modules for developers and product teams putting Ana-powered analytics inside their own application — from a one-line iframe to a fully custom chat UI driven by the API, with the auth, multi-tenancy, and production hardening done right. Total time: about 2.5 hours. Builds directly on the Developer Workshop (API & MCP) — API fundamentals (keys, the v2 REST surface, streaming basics, the sandbox) live there and aren’t re-taught; this workshop is about putting those pieces inside your product.

​

Who this is for

• Engineers embedding analytics in an internal portal or a customer-facing SaaS — you should have completed (or skimmed) the Developer Workshop first- Product teams scoping “AI analyst” features without building the analyst- Platform teams who’ll own the auth, tenancy, and cost model underneath

​

What you’ll be able to do

After module	You can…
0	Pick the right embedding surface for your product need
1	Design auth with service accounts and scoped, short-lived keys — least privilege by default
2	Drive a streamed conversation through the Chat API into your own UI
3	Fetch answers, charts, and reports for rendering in your components
4	Embed the full Ana UI or dashboards via iframe, with tools and connectors locked down per embed
5	Choose and implement a multi-tenant scoping pattern
6	Harden for production: rate behavior, timeouts, cost, and nondeterminism in UX

​

Workshop modules

Module	Time
0 · The Embedding Decision Map	00_DECISION_MAP.md	15 min
1 · Auth & Scoped Access	01_AUTH_SCOPED_ACCESS.md	20 min
2 · Embed Chat in Your App	02_EMBED_CHAT.md	25 min
3 · Embed Answers & Visuals	03_ANSWERS_VISUALS.md	20 min
4 · Embedded UI & Dashboards	04_EMBEDDED_DASHBOARDS.md	20 min
5 · Multi-Tenant Patterns	05_MULTI_TENANT.md	20 min
6 · Production Hardening	06_PRODUCTION_HARDENING.md	15 min

​

How to use this workshop

• Prerequisites: completed (or skimmed) the Developer Workshop; admin access for service-account creation; a connected data source to embed against.- Work in order — Module 1’s auth design is load-bearing for everything after it.- Code samples are curl and Python; the embedding surface details follow the current guide at docs.textql.com/core/guides/embedding-ana and the API reference — verify against them when building, as the surface evolves.- Where a capability is deployment-dependent, the module says so for that item specifically.

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.