Skip to content

Oracle Query Builder Helper

Assists with interactive Oracle query building tasks: discover tables in a schema, list columns for a table, suggest basic joins, and generate and run a simple query from natural language requirements. Returns results in text/JSON by default, with optional export formats.
Preview

Usage

Use this node early in a workflow to explore an Oracle schema and quickly assemble a starter query. Typical steps: 1) discover tables in a schema, 2) inspect columns of a target table, 3) request suggested joins, 4) describe desired data to build and run a simple query. Choose your preferred output format for display or export.

Inputs

FieldRequiredTypeDescriptionExample
credentials_pathTrueNot specifiedPath or reference to stored Oracle credentials used by the service integration.
timeoutTrueNot specifiedMaximum time in seconds to wait for the operation to complete.60
actionTrueSTRINGOperation to perform: discover_tables, get_table_columns, suggest_joins, or build_query.discover_tables
target_schemaFalseSTRINGSchema to explore. Leave empty to use the current user schema.HR
table_nameFalseSTRINGTable to inspect or base for join suggestions. Required for get_table_columns and suggest_joins.employees
query_requirementsFalseSTRINGNatural language description of the data you want. Used when action is build_query.List employees and their department names
output_formatTrueSTRINGSelect output format: text, html, xlsx, pdf, or all (generates all formats if available).text

Outputs

FieldTypeDescriptionExample
textSTRINGHuman-readable summary and, when applicable, query results in plain text.Oracle Tables in Schema: HR
jsonSTRINGRaw JSON payload of the operation result (tables, columns, suggestions, or query results).{"tables":[{"table_name":"EMPLOYEES"}]}
htmlSTRINGHTML table rendering of results when output_format is html or all.......
EMPLOYEE_ID
xlsxBYTESBinary Excel content for results when output_format is xlsx or all.
pdfBYTESBinary PDF content for results when output_format is pdf or all.

Important Notes

  • The node uses stored Oracle credentials; ensure credentials_path is valid and authorized.
  • get_table_columns and suggest_joins require table_name.
  • When action is build_query, the generated query is a simplified heuristic based on the text in query_requirements; review before using in production.
  • If target_schema is empty, operations default to the current user schema.
  • Choosing output_format = all attempts to produce text/JSON plus HTML, XLSX, and PDF variants if supported.

Troubleshooting

  • Error: Unknown action: Verify the action is one of discover_tables, get_table_columns, suggest_joins, build_query.
  • No results when discovering tables: Confirm target_schema exists and the credentials have privileges to list objects.
  • Column discovery fails: Provide a valid table_name and ensure the table is accessible in the specified or current schema.
  • Join suggestions seem generic: Suggestions are template-based; refine by specifying a precise table_name and schema.
  • Timeouts: Increase the timeout value for large schemas or heavy queries, or optimize the schema filters.