DinastiAPI User icon

DinastiAPI User

Get user information and manage presence with DinastiAPI WhatsApp API

Overview

The "DinastiAPI User" node integrates with the DinastiAPI WhatsApp API to retrieve and manage user information and presence data. It supports multiple operations such as checking if users have WhatsApp, fetching detailed user info, retrieving avatars, managing presence status, and more.

This node is beneficial in scenarios where you need to automate WhatsApp user management or gather user-related data programmatically. For example, you can verify whether a list of phone numbers are registered on WhatsApp, fetch profile pictures for contacts, or update your own presence status automatically based on external triggers.

Specifically, the Get User Info operation allows you to obtain detailed information about one or more users by providing their phone numbers or local IDs (LIDs).

Properties

Name Meaning
Phone Numbers/LIDs Comma-separated list of phone numbers or Local IDs (LIDs) to check. Examples: 5491155553934, 5491155553935, 5491155554335@lid

Note: This property is required for the Get User Info operation.

Output

The node outputs JSON data containing detailed user information returned from the DinastiAPI WhatsApp API. The exact structure depends on the API response but generally includes user details corresponding to each phone number or LID queried.

No binary data output is produced for this operation.

Dependencies

  • Requires an active connection to the DinastiAPI WhatsApp API.
  • Requires an API authentication credential configured in n8n to authorize requests.
  • Uses internal helper functions for phone number validation and API requests.

Troubleshooting

  • Invalid phone number format: Ensure phone numbers are correctly formatted and valid. The node validates phone numbers unless they are specified as LIDs (which include @lid).
  • API request failures: Network issues or invalid credentials may cause errors. Verify that the API key credential is correctly set up and has necessary permissions.
  • Empty or malformed input: The phoneNumbers property must be provided and contain at least one valid phone number or LID.
  • Handling multiple inputs: When processing multiple items, errors in one item will stop execution unless "Continue On Fail" is enabled.

Links and References

Discussion