Zalo icon

Zalo

Zalo Node
Join our community

Actions7

Overview

This node interacts with an API to retrieve information about a user. Specifically, the "Get Me" operation fetches details of a user either by a provided User ID or, if no ID is given, it retrieves information about the currently authenticated user.

Common scenarios for this node include:

  • Fetching profile details of the current user in an automation workflow.
  • Retrieving information about a specific user by their ID for further processing or decision-making.
  • Integrating user data retrieval into larger workflows that require user context.

Practical example:

  • An automation that triggers on a new event and needs to enrich the data with the current user's profile information.
  • A system that manages multiple users and needs to pull detailed info about a particular user based on their ID.

Properties

Name Meaning
User ID The ID of the user whose information you want to retrieve. If left empty, the node fetches info of the current user.
Send Option Determines the format of the message sent:
- Raw Json: Sends the message as raw JSON.
- Message: Sends the message in a predefined format.

Output

The node outputs JSON data containing the user's information retrieved from the API. The structure typically includes fields such as user identifiers, cookies, user agent strings, and other profile-related data as returned by the API.

If binary data were involved (not indicated here), it would represent associated files or media related to the user, but this node focuses on JSON user data only.

Dependencies

  • Requires access to the target API with appropriate authentication (e.g., an API key or token).
  • The node depends on HTTP request capabilities to communicate with the API endpoint.
  • Proper credentials must be configured in n8n to authorize API calls.

Troubleshooting

  • Missing or invalid User ID: If a User ID is provided but incorrect or does not exist, the API may return an error or empty response. Verify the User ID before running the node.
  • Authentication errors: Ensure that the API credentials are correctly set up and have sufficient permissions to access user information.
  • Network issues: Connectivity problems can cause request failures. Check network settings and API availability.
  • Unexpected response format: If the API changes its response schema, the node's output might not match expectations. Review API documentation for updates.

Common error messages might include:

  • Unauthorized or forbidden errors indicating credential issues.
  • Not found errors when the User ID does not correspond to any user.
  • Timeout or connection errors due to network problems.

Resolving these usually involves verifying credentials, checking User ID validity, and ensuring stable network connectivity.

Links and References

Discussion