Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to retrieve detailed information about a specific user by their unique ID. It is useful in scenarios where you need to fetch user details for workflow automation, such as syncing user data, generating reports, or triggering actions based on user attributes.
For example, you might use this node to:
- Retrieve a user's profile information before assigning tasks.
- Fetch user details to personalize notifications or emails.
- Integrate user data into other systems like CRMs or HR platforms.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user to retrieve. This is a required string input where you specify the unique identifier of the user whose information you want to get. |
Output
The node outputs JSON data representing the user object retrieved from the awork API. This typically includes fields such as user ID, name, email, role, and other profile-related information depending on the API response.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the awork API.
- The node uses the base URL
https://api.awork.comand expects JSON responses. - Proper permissions on the API key are necessary to access user data.
Troubleshooting
- Invalid User ID: If the provided User ID does not exist or is malformed, the node may return an error indicating that the user was not found. Verify the User ID is correct.
- Authentication Errors: If the API key is missing, invalid, or lacks sufficient permissions, authentication errors will occur. Ensure the API key is correctly configured and has access rights.
- Network Issues: Connectivity problems can cause request failures. Check network settings and API availability.
- Rate Limits: Excessive requests may trigger rate limiting by the awork API. Implement retries or backoff strategies if needed.
Links and References
- awork API Documentation – Official API docs for detailed user resource schema and endpoints.
- n8n Documentation – For general guidance on using credentials and configuring nodes.