Directus (DrWade) icon

Directus (DrWade)

Consume Directus API

Actions109

Overview

The Directus (DrWade) n8n node allows you to interact with the Directus API, specifically for managing users in this context.
For the Users → Get operation, the node retrieves detailed information about a specific user from your Directus instance using their unique ID.

Common scenarios:

  • Fetching user profile data for automation or reporting.
  • Validating user existence before performing further actions.
  • Integrating user details into workflows, such as sending notifications or synchronizing user data with other systems.

Example use case:
You want to retrieve and log the details of a user when they sign up, or fetch user information to personalize an email campaign.

Properties

Name Type Meaning
ID String Primary key of the user. Used to identify which user's details to retrieve.

Output

  • The output is a single object under the json field containing all available details of the requested user.
  • The structure of the returned object matches the user schema defined in your Directus instance. Typical fields may include:
    • id
    • first_name
    • last_name
    • email
    • role
    • status
    • ...and any custom fields present in your Directus setup.

Example output:

{
  "id": "72a1ce24-4748-47de-a05f-ce9af3033727",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "jane.doe@example.com",
  "role": "admin",
  "status": "active"
}

Note: The actual fields depend on your Directus configuration.

Dependencies

  • Directus API: You must have access to a running Directus instance.
  • API Credentials: The node requires valid Directus API credentials configured in n8n (directusApi).
  • Network Access: n8n must be able to reach your Directus server.

Troubleshooting

Common issues:

  • Invalid ID: If the provided user ID does not exist, the node will return an error indicating that the user was not found.
  • Authentication errors: If the API credentials are missing or incorrect, you may receive authentication/authorization errors.
  • Connection issues: Network problems between n8n and Directus can cause timeouts or connection refused errors.

Error messages and resolutions:

  • "User not found": Double-check the ID value; ensure it exists in your Directus instance.
  • "401 Unauthorized" or "403 Forbidden": Verify your API credentials and permissions.
  • "ENOTFOUND" or "ECONNREFUSED": Check your Directus server URL and network connectivity.

Links and References

Discussion