Directus (denkhaus)Install

Overview

This n8n node is designed to retrieve a specific revision by its primary key (ID) from a resource called "Revision". It is useful in scenarios where you need to fetch detailed information about a particular revision, such as for auditing changes, displaying version history, or restoring previous states of an entity.

Practical examples:

• Fetching the details of a document's revision for review.
• Displaying change logs or version history in a workflow.
• Integrating with systems that require tracking and referencing specific revisions.

Properties

Output

The output will be a JSON object containing the details of the requested revision. The exact structure depends on the underlying API but typically includes fields such as the revision's ID, timestamps, author, and any changes made in that revision.

Dependencies

• No explicit external services or API keys are mentioned in the provided code snippet.
• The node relies on internal modules (./actions/versionDescription, ./methods, ./actions/router) bundled within the custom node package.

Troubleshooting

Common issues:

• Invalid or missing ID: If the "ID" property is not provided or does not correspond to an existing revision, the node may return an error or empty result.
• API connectivity issues: If the underlying service is unavailable, you may encounter connection errors.

Error messages and resolutions:

• "Primary key of the revision is required": Ensure the "ID" field is filled in with a valid revision identifier.
• "Revision not found": Double-check the ID value; it must match an existing revision in the system.

Links and References

• n8n Documentation
• For more details on revision management, refer to your backend or API documentation related to revisions.