Wobby Docs
HomepageSign inCreate account
  • 🎊Welcome to Wobby
  • quick start
    • Access Wobby
    • Recruiting your first AI analyst
  • Agent
    • Creating an Agent
      • Link data sources to an Agent
      • Agent Instructions
      • Choose an LLM
    • Asking the Agent questions
      • How to ask data questions
  • data sources
    • Connect a data source
      • CSV files
      • PostgreSQL
      • MySQL
      • Snowflake
      • BigQuery
      • Microsoft SQL Server (MS SQL)
      • MariaDB
    • Metadata
  • Query templates
    • Quick Overview
    • Creation & Approval
    • How Agents Use Query Templates
  • Integrations
    • Slack
    • Teams
  • SECURITY & privacy
    • How Wobby protects your data
Powered by GitBook
On this page
  • Agent-Generated Templates
  • Manual Template Creation
  • Approval Process
  • Versioning and Audit Trail

Was this helpful?

  1. Query templates

Creation & Approval

There are two main ways to create query templates in Wobby:

  • AI agents can create templates during task execution

  • Users can create templates manually from the Query Templates page

Either way, every template must go through an approval step before agents can use it.


Agent-Generated Templates

When AI agents write useful SQL queries during a task, they may register it as a new template.

What happens:

  1. The query is saved as a draft template

  2. It includes SQL, table references, and auto-detected parameters

  3. The template is listed in the "Needs Approval" section

A data owner can then review and approve it.


Manual Template Creation

You can also create templates yourself directly from the Query Templates page.

Steps:

  • Write your SQL

  • Add parameters (if needed)

  • Link the appropriate tables

  • Save and submit the template for approval

This is useful when you already know which queries are needed by your team.


Approval Process

Before agents can use a query template:

  • A user with permission must review the SQL

  • Ensure the query is safe, performant, and correct

  • Toggle the approval switch to allow agent access

Approved templates are:

  • Visible to agents connected to the right tables

  • Searchable by name, tags, and description

  • Reusable across multiple tasks

Each approved version is tracked for audit purposes.


Versioning and Audit Trail

Templates are versioned. When a template is updated:

  • A new version is created

  • Each version must be approved independently

  • History includes who created, modified, and approved it

This provides a clear audit trail of how queries evolve and who’s responsible for changes.

PreviousQuick OverviewNextHow Agents Use Query Templates

Last updated 2 months ago

Was this helpful?