MySQL Execute¶
Executes non-SELECT SQL statements (INSERT, UPDATE, DELETE, DDL) against a MySQL database using provided credentials. Returns a human-readable summary and a JSON payload of the execution result. Useful for data modification and administrative operations rather than data retrieval.
Usage¶
Use this node when you need to modify data or schema in a MySQL database as part of a workflow (e.g., insert new records, update fields, delete rows, or run DDL statements). Provide a valid credentials path and your SQL statement. The node performs the request and returns a formatted text summary along with a JSON result that can be consumed by downstream nodes.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | Not specified | Path or reference to the stored MySQL credentials that the node will use to authenticate. | |
| timeout | True | Not specified | Maximum time (in seconds) to wait for the execution request to complete before failing. | 60 |
| sql_text | True | STRING | The SQL statement to execute. Intended for INSERT/UPDATE/DELETE statements and DDL (e.g., CREATE TABLE, ALTER TABLE). | INSERT INTO users (name, email) VALUES ('John Doe', 'john@example.com') |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Formatted summary of the execution (e.g., title and affected rows or status message). | MySQL Execute Results: 1 row affected |
| json | STRING | JSON string with the raw execution result returned by the service (e.g., affected row count, status, or error). | {"rows_affected": 1, "status": "success"} |
| html | STRING | HTML output placeholder. For execute operations, this will typically be empty. | |
| xlsx | BYTES | Binary XLSX data placeholder. For execute operations, this will typically be empty. | |
| BYTES | Binary PDF data placeholder. For execute operations, this will typically be empty. |
Important Notes¶
- Write operations only: This node is intended for non-SELECT statements. Use the MySQL Query node for data retrieval.
- Credentials required: The node will fail if the credentials path is missing or invalid.
- Execution timeout: Long-running statements may time out; adjust the timeout input as needed.
- Result content: The text output provides a human-readable summary, while the JSON output contains the structured result. The HTML/XLSX/PDF outputs are typically empty for execute operations.
- SQL safety: Ensure your SQL is parameterized or sanitized in upstream logic to avoid injection risks.
Troubleshooting¶
- SQL syntax error: Verify the SQL statement in sql_text is valid for MySQL and that table/column names are correct.
- Authentication/permission denied: Confirm the credentials_path points to valid MySQL credentials and that the user has permissions to perform the operation.
- Timeouts: Increase the timeout if the database is under heavy load or the statement is expected to take longer.
- Connectivity issues: Check network access, firewall rules, and that the MySQL server is reachable from the execution environment.
- No rows affected: This may indicate that the WHERE clause matched no records. Double-check your conditions.