Directus icon

Directus

Consume Directus API

Actions109

Overview

This node integrates with the Directus API to perform operations on various Directus resources. Specifically, for the Users resource with the Get operation, it retrieves detailed information about a single user by their unique identifier (ID). This is useful in scenarios where you need to fetch user profile data, verify user details, or integrate user information into workflows.

Practical example:
You might use this node to get the profile details of a user who just signed up or to retrieve user metadata before performing further actions like sending personalized emails or updating related records.

Properties

Name Meaning
ID The primary key (unique identifier) of the user to retrieve. This is required and should be provided as a string, e.g., "72a1ce24-4748-47de-a05f-ce9af3033727".

Output

The output is a JSON object representing the user data retrieved from the Directus API. It contains all available fields for the specified user, such as email, role, status, and any custom fields defined in your Directus instance.

Example output structure (simplified):

{
  "id": "72a1ce24-4748-47de-a05f-ce9af3033727",
  "email": "user@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "role": "editor",
  "status": "active",
  "...": "other user fields"
}

No binary data is output for 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 and requires appropriate permissions to read user data.
  • No additional external dependencies beyond the Directus API and configured credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing user ID: The node requires a valid user ID; ensure the ID is correct and exists in Directus.
    • Insufficient permissions: The API key used must have permission to read user data.
    • Network or authentication errors: Verify that the Directus API URL and credentials are correctly configured.

  • Common error messages:

    • "User not found": The provided ID does not correspond to any user.
    • "Unauthorized" or "Forbidden": The API key lacks necessary permissions.
    • "Invalid credentials": The API key or token is incorrect or expired.

  • Resolution tips:

    • Double-check the user ID input.
    • Confirm API credentials and permissions in Directus.
    • Test connectivity to the Directus API endpoint outside n8n if needed.

Links and References

This summary focuses solely on the "Users" resource with the "Get" operation as requested, based on static analysis of the provided source code and property definitions.

Discussion