Release Notes

Updates to Taufinity Studio are released regularly. This page lists what changed in each release, focusing on what it means for your workflow.

March 26, 2026

Reports & Dashboards — Interactive dashboards with KPI cards, stacked bar charts, and data tables powered by BigQuery. Click chart segments to drill down into filtered table views. AI-generated insights analyze your data automatically using playbooks — cached by content so repeated views load instantly.
Whitelabel Portal — Access Taufinity Studio on your own branded domain with custom logo, colors, title, and favicon. Google SSO works seamlessly across portal domains with secure token-based session handoff. Available on *.taufinity.io subdomains; custom domains coming soon.
Playbook Lock — Lock playbooks to prevent accidental edits while they're running in production. Unlocking requires explicit confirmation.

Dashboard drill-down — Charts and tables are linked: click a bar chart segment to filter the table below. Filter state is preserved in the URL for sharing and browser navigation.
Playbook run summaries — Playbook runs now show created task counts in the summary view, making it easier to see what each run accomplished.

Ask Data (text-to-SQL) — Ask natural language questions about your data directly in the widget chat. The AI translates your question into SQL, executes it against your BigQuery provider, and returns the results. Your data is always filtered to your organisation — cross-tenant access is not possible. Enable the ask_data tool in your widget's Agent settings.

OpenAI-compatible API — Use any OpenAI SDK or tool to interact with your widgets. Point your existing code at /v1/chat/completions with model widget:<uuid> and it works out of the box, including streaming support.
Scheduled playbooks — Run playbooks on a recurring schedule (hourly, daily, weekly). Set a cron expression, pick a timezone, and playbooks execute automatically. Auto-pauses after repeated failures to prevent runaway costs.

Chat conversation compaction — Fixed an issue where conversation compaction could fail with a "not found" error.