Actions26
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node allows you to retrieve detailed information about a specific user from the awork API by providing their User ID. It is useful in scenarios where you need to fetch user details for automation workflows, such as looking up user profiles, verifying user existence, or integrating user data into other systems.
Example use cases:
- Fetching user details to enrich CRM records.
- Validating a user's presence before assigning tasks.
- Displaying user information in automated reports.
Properties
| Display Name | Type | Description |
|---|---|---|
| User ID | String | The ID of the user to retrieve. Required. |
- User ID: Enter the unique identifier of the user whose information you want to fetch.
Output
The output will be a JSON object containing the details of the requested user. The structure typically includes fields such as user ID, name, email, and other profile information as provided by the awork API.
{
"id": "string",
"name": "string",
"email": "string",
// ...other user fields
}
Note: The exact fields depend on the awork API's response.
Dependencies
- External Service: Requires access to the awork API.
- API Credentials: You must configure valid
aworkApicredentials in n8n. - Environment: No special environment variables are required beyond standard n8n credential setup.
Troubleshooting
- Invalid User ID: If an incorrect or non-existent User ID is provided, the node may return an error or an empty result. Double-check the User ID value.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure your
aworkApicredentials are correctly set up in n8n. - Network Issues: Connectivity problems with the awork API endpoint (
https://api.awork.com) can lead to request failures.
Common error messages:
"User not found": The specified User ID does not exist. Verify the ID."401 Unauthorized": Check your API credentials."Network Error": Ensure n8n can reach the awork API.