Overview
This node executes SQL statements on an Oracle database. It is designed to run queries or commands by connecting to an Oracle DB instance using provided credentials and returning the results as JSON data.
Common scenarios where this node is useful include:
- Retrieving data from Oracle tables with SELECT queries.
- Running DML operations like INSERT, UPDATE, DELETE.
- Executing parameterized queries to safely inject user inputs.
- Automating database tasks within n8n workflows.
For example, you could use it to fetch product details with a query like SELECT id, name FROM product WHERE id < :param_name and pass the parameter dynamically from previous workflow steps.
Properties
| Name | Meaning |
|---|---|
| SQL Statement | The SQL statement to execute on the Oracle database. Supports parameter placeholders prefixed with : (e.g., :param_name). |
| Parameters | A collection of parameters to bind to the SQL statement. Each parameter includes: - Name: The placeholder name without the colon prefix. - Value: The value to bind. - Data Type: Either "String" or "Number". - Parse for IN Statement: If set to "Yes", treats the value as a comma-separated list and expands it into multiple bind variables for use in an SQL IN clause. |
Output
The output is a JSON array representing the rows returned by the executed SQL query. Each element corresponds to a row, with key-value pairs matching column names and their values.
If the SQL statement does not return rows (e.g., an INSERT), the output will be an empty array.
No binary data output is produced by this node.
Dependencies
- Requires an Oracle database accessible via connection credentials.
- Needs an API key credential providing username, password, and connection string for the Oracle DB.
- Uses the official OracleDB Node.js driver internally.
- No additional environment variables are required beyond the configured credentials.
Troubleshooting
- Connection errors: Ensure the Oracle DB credentials (user, password, connection string) are correct and the database is reachable from the n8n instance.
- SQL syntax errors: Verify the SQL statement syntax is valid for Oracle. Parameter placeholders must match the names defined in the Parameters property without the colon prefix.
- Parameter binding issues: When using the "Parse for IN Statement" option, ensure the value is a properly formatted comma-separated string without spaces unless intended.
- Resource cleanup: The node attempts to close the database connection after execution; if errors occur during closing, they are logged but do not fail the node.
- Unsupported features: This node does not support returning binary data or LOBs directly.