Overview
This node, named "Speedy Message Node," is designed to send messages through a database stored procedure call. It constructs and executes an SQL query that calls a stored procedure (n8n_sendMessage) with parameters such as sender, receiver, subject, text, type, and flag. The node reads configuration from an external INI file to connect to a MySQL database and sends the message by executing the SQL command.
Common scenarios where this node is beneficial:
- Automating message sending workflows where messages are managed via a database.
- Integrating messaging functionality into broader automation pipelines that use n8n.
- Sending notifications or alerts by invoking a predefined stored procedure in a MySQL database.
Practical example:
You want to send a notification email or internal message to a user when a certain event occurs. This node can be configured with the recipient's address, subject, and message text, then it will execute the stored procedure to send the message accordingly.
Properties
| Name | Meaning |
|---|---|
| Empfänger | Sets the recipient of the message (Receiver). |
| Betreff | Sets the subject of the message (Subject). |
| Text | Sets the text content of the message (Text). |
Output
The node outputs an array of JSON objects under the json field. Each object contains a queryResult property which holds the result returned from the execution of the SQL query (i.e., the stored procedure call). This typically includes any data or status returned by the database after sending the message.
No binary data output is produced by this node.
Dependencies
- Requires a MySQL database accessible with credentials and connection details either provided directly or loaded from an external INI configuration file (
speedy_config.json). - The node depends on the presence of a stored procedure named
n8n_sendMessagein the target database. - Requires the
mysqlpackage for database connectivity. - Reads configuration from a JSON file (
speedy_config.json) and an INI file whose path is specified inside that JSON.
Troubleshooting
- Database connection errors: Ensure the database server, port, username, password, and database name are correctly set either in the node parameters or the INI configuration file.
- Missing or incorrect stored procedure: The stored procedure
n8n_sendMessagemust exist in the database and accept the expected parameters. If not, the SQL query will fail. - Empty required fields: The node requires at least the receiver and text fields to be non-empty to construct the SQL call. Missing these may cause no message to be sent.
- SQL injection risk: Since the SQL query is constructed by interpolating parameters directly into the string, ensure inputs are sanitized or controlled to avoid injection vulnerabilities.
- Error executing SQL query: Errors during query execution are logged to the console. Check logs for detailed error messages and verify database permissions and query correctness.