Actions109
- Activity Actions
- Assets Actions
- Authentication Actions
- Collections Actions
- Extensions Actions
- Fields Actions
- Files Actions
- Folders Actions
- Items Actions
- Permissions Actions
- Presets Actions
- Relations Actions
- Revisions Actions
- Roles Actions
- Settings Actions
- Users Actions
- Utilities Actions
- Webhooks Actions
Overview
This node integrates with the Directus API to perform various operations on different Directus resources. Specifically, for the Revisions resource with the Get operation, it retrieves a single revision record by its primary key (ID). This is useful when you want to fetch detailed information about a specific revision entry in your Directus project.
Common scenarios include:
- Auditing changes made to data by fetching revision details.
- Displaying historical versions of content or records.
- Integrating revision data into workflows for review or processing.
Example: You have a revision ID and want to get all metadata and details about that revision to display or process further in your workflow.
Properties
| Name | Meaning |
|---|---|
| ID | The primary key of the revision to retrieve. This is a required string input identifying the specific revision record. |
Output
The node outputs the JSON representation of the requested revision object from Directus. The output contains all fields and metadata associated with that revision as returned by the Directus API.
The output structure is a JSON object representing the revision, including properties such as revision ID, related item, user who made the revision, timestamp, and any other revision-specific data.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Directus instance via an API key credential configured in n8n.
- The node uses the Directus REST API endpoints to fetch revision data.
- Proper permissions in Directus are necessary to access revision records.
Troubleshooting
- Error: Revision not found — Ensure the provided revision ID exists in the Directus project.
- Authentication errors — Verify that the API key credential is valid and has sufficient permissions.
- Network issues — Check connectivity to the Directus server.
- Invalid ID format — Confirm the ID is correctly formatted as expected by Directus (usually a UUID or numeric ID).
If the node throws an error, enabling "Continue On Fail" can help handle errors gracefully within workflows.
Links and References
This summary focuses on the "Revisions" resource with the "Get" operation as requested, based on static analysis of the provided source code and property definitions.