Actions12
Overview
This node interacts with the Zalo platform to retrieve user information. Specifically, the "Lấy Thông Tin Người Dùng" (Get User Information) operation fetches detailed data about a specified Zalo user by their User ID. This is useful in scenarios where you need to enrich workflows with user profile details from Zalo, such as integrating contact information into CRM systems, personalizing communications, or verifying user identities.
Practical examples:
- Automatically fetching and displaying user profile details when processing customer support tickets.
- Enriching marketing automation workflows with user demographic data from Zalo.
- Validating user identity during onboarding processes by retrieving official Zalo user info.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the Zalo user whose information you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing the detailed information of the requested Zalo user. The structure typically includes fields representing the user's profile attributes as returned by the Zalo API. The exact fields depend on the API response but generally include identifiers, display names, avatar URLs, and other profile metadata.
No binary data output is produced by this operation.
Example output JSON structure (simplified):
{
"userId": "123456789",
"name": "Nguyen Van A",
"avatarUrl": "https://example.com/avatar.jpg",
"gender": "male",
"birthday": "1990-01-01",
"status": "active"
}
Dependencies
- Requires an active connection to the Zalo API via an API key credential configured in n8n.
- The node depends on proper authentication credentials to access user data.
- Network connectivity to Zalo's API endpoints is necessary.
- No additional external services are required beyond the Zalo API.
Troubleshooting
Common issues:
- Invalid or missing User ID parameter will cause the operation to fail.
- Expired or incorrect API credentials will result in authentication errors.
- Network issues or Zalo API downtime can cause request failures.
Error messages:
"NodeOperationError"with messages related to authentication failure indicates invalid API credentials; verify and update your API key.- Errors indicating
"User not found"suggest the provided User ID does not exist or is inaccessible; double-check the User ID. - Timeout or network errors require checking internet connectivity and Zalo API status.
Resolution tips:
- Ensure the User ID is correctly entered and corresponds to an existing Zalo user.
- Confirm that the API key credential is valid and has sufficient permissions.
- Retry after some time if the issue is due to temporary network or service disruptions.