DinastiAPI User icon

DinastiAPI User

Get user information and manage presence with DinastiAPI WhatsApp API

Overview

This node interacts with the DinastiAPI WhatsApp API to retrieve user-related information and manage presence. Specifically, the "Get LID From Phone" operation allows users to obtain the Local ID (LID) associated with a given phone number or JID (Jabber ID). This is useful in scenarios where you need to map a phone number or JID to its internal local identifier used by the WhatsApp system via DinastiAPI.

Practical examples include:

  • Integrating WhatsApp user identification into CRM systems by converting phone numbers to LIDs.
  • Automating workflows that require referencing users by their LID rather than phone numbers.
  • Synchronizing contact data between different systems using LIDs as unique identifiers.

Properties

Name Meaning
Phone Number or JID The phone number or Jabber ID (JID) for which to retrieve the Local ID (LID). Examples: 5491155553934 or 5491155553934@s.whatsapp.net. This field is required for the operation.

Output

The output JSON contains the response from the DinastiAPI endpoint /user/lid/get, which returns the Local ID (LID) corresponding to the provided phone number or JID.

The structure typically includes fields such as the LID string and possibly additional metadata related to the user. The exact structure depends on the API response but generally provides the LID needed for further processing.

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the DinastiAPI WhatsApp API.
  • Requires an API key credential configured in n8n to authenticate requests to DinastiAPI.
  • The node uses the DinastiAPI endpoint /user/lid/get via a POST request with the phone number/JID as payload.

Troubleshooting

  • Common issues:

    • Invalid or improperly formatted phone number or JID input may cause the API to return errors or no results.
    • Missing or incorrect API credentials will result in authentication failures.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Errors returned from the API typically include messages indicating invalid input or unauthorized access.
    • If the node throws an error about missing parameters, ensure the "Phone Number or JID" property is correctly set and not empty.
  • Resolutions:

    • Validate phone numbers before inputting them, ensuring they follow international format without extra characters unless specifying a JID.
    • Verify that the API key credential is properly configured and has necessary permissions.
    • Check network connectivity and API service status if requests fail repeatedly.

Links and References

Discussion