Speedy Get Property Node icon

Speedy Get Property Node

speedy Property Node for getting the properties of an Speedy document

Speedy Get Property Node

AI-generated

Overview

This node, named "Speedy Get Property Node," is designed to retrieve properties of a Speedy document from a MySQL database. It allows users to query document properties based on either a document number, an object ID, or other identifiers. This node is useful in scenarios where you need to fetch metadata or attributes related to documents stored in a Speedy system, such as document management or archival workflows.

Practical examples include:

  • Retrieving detailed properties of a document by its document number to display or process further.
  • Fetching container path information for an object ID to understand the document's storage hierarchy.
  • Custom SQL queries to extract specific document-related data from the Speedy database.

Properties

Name Meaning
Dokumentennummer The document number for which the properties are needed.
Object-ID The object ID for which the properties are needed.

Output

The node outputs JSON arrays containing the results of the executed SQL queries. The output includes:

  • Document properties retrieved via stored procedures based on the provided document number or object ID.
  • Container path information associated with the object ID, returned as a separate JSON object with a field like ctnr_fullname.

No binary data output is produced by this node.

Dependencies

  • Requires access to a MySQL database where the Speedy system's stored procedures and tables reside.
  • Reads configuration from a JSON file (speedy_config.json) and an INI file specified within that JSON to obtain default database connection parameters.
  • Uses the mysql Node.js package for database connectivity.
  • Requires proper credentials (server, user, password, database, port) either from input data or configuration files.

Troubleshooting

  • Database Connection Errors: Ensure that the MySQL server details (host, user, password, database, port) are correct and accessible from the n8n environment.
  • Missing or Incorrect Parameters: If neither document number nor object ID is provided, the node will not construct a valid query. Make sure to supply at least one identifier.
  • SQL Execution Failures: Errors during SQL calls may occur if the stored procedures (n8n_getDocPropDocNo, n8n_getDocPropDocID, n8n_getDocPropCtnrID, GetContainerPath) do not exist or have issues. Verify these procedures exist and function correctly in the database.
  • Configuration File Issues: The node depends on external config files; ensure speedy_config.json and the referenced INI file exist and contain valid settings.
  • Unhandled Exceptions: The node logs errors to the console but does not throw them explicitly; check n8n logs for detailed error messages.

Links and References

Discussion