Overview
This node, named "Speedy Set Property Node," is designed to set properties on a document identified by a document number within a Speedy system. It connects to a MySQL database and executes a stored procedure to update or set a property value for a given document.
Common scenarios where this node is useful include:
- Automating the update of metadata or custom properties on documents managed in a Speedy system.
- Integrating document property updates into larger workflows, such as after document processing or validation steps.
- Setting dynamic attributes on documents based on workflow data or external inputs.
For example, you might use this node to set a "Status" property to "Reviewed" on a document with a specific document number after a review process completes.
Properties
| Name | Meaning |
|---|---|
| Dokumentennummer | The document number for which the property should be set. |
| Eigenschaften Name | The name of the property to set on the document. |
| Wert | The value to assign to the specified property. |
Output
The node outputs an array of JSON objects representing the results of the property setting operations. However, in the current implementation, the output array is always empty ([]), indicating no direct data is returned from the database call to the workflow.
No binary data output is produced by this node.
Dependencies
- MySQL Database: The node requires access to a MySQL database where the Speedy system's stored procedure
n8n_SetPropertyis defined. - Configuration File: It reads configuration parameters (such as server, database, user, password, port) from an INI file whose path is specified in a JSON config file (
speedy_config.json). - Stored Procedure: The database must have a stored procedure named
n8n_SetPropertythat accepts three parameters: document number, property name, and property value.
Troubleshooting
- Database Connection Issues: If the node cannot connect to the MySQL database, verify the credentials and connection details in the INI configuration file and ensure the database server is accessible.
- Missing Document Number or Property Name: The node requires both a document number and a property name to function. If either is missing, the property will not be set.
- Stored Procedure Errors: Errors during execution of the stored procedure
n8n_SetPropertyare logged to the console. Common causes include incorrect procedure definition or insufficient database permissions. - Empty Output: Since the node does not return data from the database call, lack of output does not necessarily indicate failure. Check logs for errors.