OptionalAutoWhen true, the server will automatically resolve name collisions by appending sequential numeric suffixes (e.g., "Name (1)", "Name (2)") instead of returning an error. The resolved name is returned in the result's Query.Name field.
OptionalCategoryOptional existing category ID to assign the query to
OptionalCategoryOptional category path for automatic hierarchy creation (e.g., "Reports/Sales/Monthly") - takes precedence over CategoryID
OptionalDescriptionOptional general description of what the query does
OptionalExecutionOptional execution cost indicator (higher = more expensive to run)
OptionalFeedbackOptional user feedback about the query
Required name for the query (must be unique within category)
OptionalOriginalOptional original SQL before optimization or modification
OptionalParameterOptional caller-provided parameter sample values. When provided, these override LLM-generated sampleValues during the extraction pipeline. Each entry maps a parameter name to a tested/validated sample value.
OptionalPermissionsOptional array of permissions to create for the query
OptionalQualityOptional quality indicator (higher = better quality, defaults to 0)
OptionalSQLOptional SQL query text to execute (can contain Nunjucks template syntax)
OptionalStatusOptional query approval status (defaults to 'Pending')
OptionalTechnicalOptional technical documentation for developers
OptionalUserOptional natural language question this query answers
OptionalUsesOptional flag indicating if the query uses Nunjucks template syntax (auto-detected if not specified)
Input type for CreateQuery mutation calls - creates a new query with optional hierarchical category path