Actions16
Overview
This node interacts with the Dingtalk API to query detailed information about a specific user. It is useful in scenarios where you need to retrieve user profile data, such as fetching contact details, roles, or status within an organization. For example, it can be used in HR automation workflows to pull up employee information based on their user ID.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose details are being queried. This is a required string input. |
Output
The node outputs JSON data containing the detailed information of the requested user. The exact structure depends on the Dingtalk API response but typically includes fields like user name, email, department, position, and other profile attributes.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Dingtalk API.
- The node depends on the Dingtalk API service being accessible.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing User ID will cause the API call to fail.
- Network connectivity problems may prevent successful API requests.
- Insufficient permissions or invalid API credentials will result in authorization errors.
Error messages:
"Operation "user.get" not found": Indicates the specified operation is not recognized; ensure the correct operation name is used.- API error messages returned from Dingtalk (e.g., user not found) will be passed through; verify the User ID is correct.
- If the node throws an error related to credentials, check that the API key is properly configured and has necessary permissions.
Links and References
- Dingtalk Official API Documentation
- n8n Documentation on Creating Custom Nodes