Oracle Query Builder Helper
An interactive helper for exploring Oracle schemas and drafting queries. It can discover tables, list columns, suggest simple JOIN relationships, and generate a basic query from natural-language requirements. Results can be returned as text/JSON or exported to HTML, Excel, and PDF based on the chosen output format.
Usage
Use this node when you need guided exploration of an Oracle database and a quick way to assemble starter queries. Typical workflow: provide credentials, use discover_tables to enumerate tables in a schema, get_table_columns to inspect a table, suggest_joins for basic relationship hints, and build_query to produce a simple query and run it. Choose output_format to control whether you get rich exports or just text/JSON.
| Field | Required | Type | Description | Example |
|---|
| credentials_path | True | STRING | Path or reference to saved Oracle credentials (matches the 'oracle' credential template). | /data/credentials/oracle.json |
| timeout | True | INT | Request timeout in seconds for operations executed by this node. | 120 |
| action | True | STRING | Operation to perform. Options: discover_tables (list tables), get_table_columns (list columns for a table), suggest_joins (basic join hints), build_query (generate and execute a simple query from requirements). | discover_tables |
| target_schema | True | STRING | Schema to explore. Leave empty to use the current user schema. | HR |
| table_name | True | STRING | Table name to inspect or use for join suggestions. Required for get_table_columns and suggest_joins; otherwise unused. | EMPLOYEES |
| query_requirements | True | STRING | Natural-language description of what you want to retrieve for the build_query action. | List employees with their department names where salary is above 70000 |
| output_format | True | STRING | Controls the format of the returned results. Options: text, html, xlsx, pdf, all. The 'all' option returns all formats. | text |
Outputs
| Field | Type | Description | Example |
|---|
| text | STRING | Human-readable text summary or table preview of the result. Always included when output_format is text or all. | Oracle Tables in Schema: HR - EMPLOYEES - DEPARTMENTS ... |
| json | STRING | JSON-serialized data for programmatic use, including any result metadata. Always included when output_format is text or all. | {"tables": ["EMPLOYEES", "DEPARTMENTS"]} |
| html | STRING | HTML table markup for rendering results. Included when output_format is html or all; otherwise empty. | |
| xlsx | STRING | A reference or encoded payload for an Excel export of the result set. Included when output_format is xlsx or all; otherwise empty. | |
| pdf | STRING | A reference or encoded payload for a PDF export of the result set. Included when output_format is pdf or all; otherwise empty. | |
Important Notes
- Action-specific inputs: table_name is required for get_table_columns and suggest_joins; query_requirements is used by build_query.
- Output selection: output_format controls which outputs are populated. Use 'all' to receive text, json, html, xlsx, and pdf together.
- Discover vs. execute: discover_tables, get_table_columns, and suggest_joins return metadata. build_query constructs a simple query and executes it.
- Join suggestions are basic: The join suggestions are heuristic and meant as starting points; validate them against your schema.
- Schema handling: Leaving target_schema empty uses the current user schema on the Oracle instance.
- Credentials: Ensure the credentials at credentials_path match the 'oracle' template and have permissions to list schemas/tables and run queries.
Troubleshooting
- Missing table_name: For get_table_columns or suggest_joins, provide table_name. The node will raise an error if it's empty.
- No tables returned: Verify target_schema is correct and the user has access. Try leaving target_schema empty to use the default schema.
- Timeouts: Increase the timeout value for large schemas or long-running queries.
- Permission errors: Ensure the provided credentials have SELECT privileges on the target schema/tables.
- Empty exports: If html/xlsx/pdf outputs are empty, confirm output_format includes those formats (e.g., set to html/xlsx/pdf or all).
- Unexpected query from build_query: The builder is simplistic; refine query_requirements or manually edit the resulting SQL using a separate query node.