DinastiAPI User

Overview

The "DinastiAPI User" node interacts with the DinastiAPI WhatsApp API to retrieve and manage user-related information and presence status. It supports multiple operations such as checking if users have WhatsApp, retrieving avatars, getting business profiles, managing presence, and more.

A common use case is verifying whether a list of phone numbers or local IDs (LIDs) correspond to active WhatsApp users. This can be useful for contact validation before sending messages. Other scenarios include fetching user avatars, updating presence status, or obtaining detailed user info.

For example, you might input a comma-separated list of phone numbers and LIDs to check their WhatsApp availability, or request the avatar image of a specific user.

Properties

This property is required for the "Check Users" and "Get User Info" operations.

Output

The node outputs JSON data containing the response from the DinastiAPI WhatsApp API corresponding to the selected operation.

• For the "Check Users" operation, the output includes information about whether each provided phone number or LID has an associated WhatsApp account.
• If the "Get Avatar" operation is used with the option to save as binary enabled, the node outputs the avatar image either as a URL or as binary data attached to the specified binary property name. The binary data includes the base64-encoded image, MIME type, file extension, and filename.
• Other operations return relevant JSON structures such as contact lists, business profiles, presence statuses, or privacy settings.

If binary data is output (e.g., avatar images), it can be used downstream in workflows that handle files or media.

Dependencies

• Requires an API key credential for authenticating with the DinastiAPI WhatsApp API.
• The node uses HTTP requests to communicate with the external DinastiAPI service.
• Proper configuration of the API credential within n8n is necessary for successful operation.

Troubleshooting

• Invalid phone number format: The node validates phone numbers; ensure numbers are correctly formatted without extra characters except for the @lid suffix when specifying local IDs.
• API authentication errors: Verify that the API key credential is correctly set up and has the necessary permissions.
• Empty or malformed responses: Check that the input phone numbers or LIDs exist and are valid in the WhatsApp system.
• Binary data issues: When saving avatars as binary, ensure the binary property name is unique and does not conflict with other binary data in the workflow.
• Network or API downtime: External API calls may fail due to network issues or service outages; retry or check service status accordingly.

Links and References

• DinastiAPI WhatsApp API Documentation (example link, replace with actual)
• n8n documentation on Creating Custom Nodes
• n8n documentation on Working with Binary Data