Actions111
- Item Actions
- Webhook Actions
- Collection Actions
- File Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Extension Actions
- Field Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node retrieves information about a specific user from a Directus v1 API instance. It is useful in workflows where you need to fetch user details by their unique identifier, such as for user management, profile lookups, or integrating user data into other systems.
Example scenarios:
- Fetching user details to enrich records in another system.
- Validating if a user exists before performing further actions.
- Displaying user profiles in dashboards or reports.
Properties
| Name | Meaning |
|---|---|
| ID | Primary key of the user. This is a required string value representing the user's unique identifier (e.g., "72a1ce24-4748-47de-a05f-ce9af3033727"). |
Output
The output will be a JSON object containing the details of the user corresponding to the provided ID. The structure typically includes fields such as user ID, name, email, and any other properties defined in your Directus instance's user schema.
Dependencies
- Directus v1 API: You must have access to a running Directus v1 instance.
- API Credentials: Depending on your Directus setup, authentication (such as an API token) may be required. Ensure that n8n is configured with the necessary credentials to access the Directus API.
Troubleshooting
- Invalid User ID: If the provided ID does not exist, the node may return an error or an empty result. Double-check the ID value.
- Authentication Errors: If credentials are missing or incorrect, you may receive authentication or authorization errors. Ensure your API key or credentials are set up correctly in n8n.
- Connection Issues: Network problems or incorrect API URLs can cause connection failures. Verify the Directus API endpoint configuration.