Directus (denkhaus)Install

Overview

The Activity: Get operation retrieves a specific activity record by its ID from the connected service (likely Directus, based on the node name). This node is useful when you need to fetch detailed information about a particular activity, such as for reporting, auditing, or displaying activity details in workflows. For example, you might use this node to look up an activity log entry by its unique identifier and include selected fields or metadata in your automation.

Properties

Output

• The output will be a JSON object containing the details of the requested activity.
• The structure of the output depends on the selected "Fields" and "Meta" options:
  • If "Fields" is specified, only those fields are included.
  • If "Meta" is specified, additional metadata is included in the response.
• Example output:

{
  "id": 1,
  "field1": "value",
  "field2": "value",
  "meta": {
    "created_at": "2024-06-01T12:00:00Z"
  }
}

• The actual fields and meta content depend on the configuration and the underlying data model.

Dependencies

• Requires access to a Directus API endpoint.
• May require authentication credentials (API key, token, or similar) configured in n8n.
• No external npm dependencies beyond the bundled code.

Troubleshooting

• Invalid ID: If the provided ID does not exist, the node may return an error or an empty result. Ensure the ID is correct and exists in the system.
• Missing Authentication: If authentication is not set up correctly, you may receive authorization errors. Check your credentials and connection settings.
• Field/Meta Typos: Incorrect field or meta names may result in missing data or errors. Double-check spelling and available fields in your Directus instance.

Links and References

• Directus Documentation
• n8n Documentation: Custom Nodes