MySQL Execute¶
Executes MySQL data-changing statements (INSERT, UPDATE, DELETE, DDL). It uses stored credentials to connect and returns a human-readable summary along with the raw JSON response.
Usage¶
Use this node to perform non-SELECT operations against a MySQL database. Typical workflows include inserting new records, updating existing rows, deleting data, or running schema changes. Place it after a credentials/secret selection step and before any nodes that depend on side effects (e.g., verification queries or downstream processing).
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | STRING | Path or reference to stored MySQL credentials matching the 'mysql' template. Used by the node to authenticate with the database. | /secrets/mysql/prod |
| timeout | False | INT | Maximum time in seconds to wait for the execute request to complete before failing. | 30 |
| sql_text | True | STRING | SQL statement to execute. Intended for INSERT, UPDATE, DELETE, and DDL operations (non-SELECT). | INSERT INTO users (name, email) VALUES ('John Doe', 'john@example.com') |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | STRING | Formatted summary of the execution result (e.g., affected rows, success message). | MySQL Execute Results: 1 row affected |
| json | JSON | Raw JSON response from the service, which may include affected row counts, status, and any returned metadata. | {"status":"success","affected_rows":1} |
| html | HTML | HTML output placeholder (empty for this node). | |
| xlsx | XLSX | XLSX output placeholder (empty for this node). | |
| PDF output placeholder (empty for this node). |
Important Notes¶
- Non-SELECT only: Designed for INSERT/UPDATE/DELETE and DDL. Use a query node for SELECT statements.
- Credentials required: Ensure the provided credentials path refers to a valid MySQL credential set.
- Execution effects: Operations are executed directly on the target database. Validate idempotency when re-running flows.
- Timeouts: Long-running statements may need increased timeout values.
- SQL injection: Avoid interpolating untrusted input directly into SQL strings.
Troubleshooting¶
- Syntax error: Verify the SQL statement syntax is valid for MySQL and that referenced tables/columns exist.
- Permission denied: Ensure the database user has sufficient privileges for the operation.
- Connection timeout: Increase the timeout input or check network connectivity and database availability.
- No rows affected: Confirm WHERE clauses and target data match; verify the statement against the current dataset.
- Invalid credentials path: Provide a correct credentials_path that matches a valid 'mysql' credential template.