Actions7
Overview
This node allows executing SQL queries directly against a database via a "Direct Database" connection type. Specifically, for the Query resource and Execute Query operation, it executes a user-provided SQL query with optional parameters on the connected database.
Common scenarios include:
- Retrieving data from SAP Business One database tables using custom SQL.
- Running complex queries that are not supported by standard API endpoints.
- Fetching filtered or aggregated data dynamically based on workflow inputs.
Practical example:
- You want to get all business partners with a specific card code. You write a SQL query like
SELECT * FROM OCRD WHERE CardCode = @cardCodeand pass{ "cardCode": "C20000" }as query parameters. The node executes this query and returns matching records.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Type of connection to use: - Direct Database (executes SQL queries directly) - Service Layer (not applicable for this operation) |
| SQL Query | The SQL query string to execute. Must be valid SQL syntax for the target database. |
| Query Parameters | Optional JSON object containing parameters to bind in the SQL query (e.g., { "param": "value" }). |
Output
The node outputs an array of JSON objects under the json field, each representing the result of the executed SQL query. The structure depends on the query but typically includes rows returned by the query with column names as keys.
No binary data output is produced by this operation.
Example output snippet:
{
"json": {
"results": [
{ "CardCode": "C20000", "CardName": "Customer A", ... },
{ "CardCode": "C20001", "CardName": "Customer B", ... }
]
}
}
Dependencies
- Requires an active connection to the Unified MCP Server configured with appropriate credentials including an API URL and authentication token.
- For the "Direct Database" connection type, the MCP server must have direct database access enabled and properly configured.
- No additional external services are required beyond the MCP API.
Troubleshooting
- Invalid SQL syntax error: Ensure your SQL query is syntactically correct and compatible with the underlying database.
- Parameter binding issues: Verify that the JSON object for query parameters matches the placeholders used in the SQL query.
- Connection errors: Confirm that the MCP API URL and credentials are correctly set up and that the MCP server is reachable.
- Empty results: Check if the query filters or parameters are too restrictive or incorrect.
- JSON parsing errors: Make sure the "Query Parameters" input is valid JSON.