WasenderAPI icon

WasenderAPI

Manage WasenderAPI sessions, messages, contacts, and groups

Actions53

Contact → Get LID From Phone

AI-generated

Overview

This node operation retrieves the LID (likely a unique identifier) associated with a given phone number or JID (Jabber ID) from the WasenderAPI contact resource. It is useful in scenarios where you need to map a phone number to its corresponding LID within the WhatsApp session managed by WasenderAPI. For example, it can be used to verify contact identities or integrate with systems that require the LID instead of the phone number.

Use Case Examples

  1. Given a phone number or JID, the node fetches the corresponding LID from the WasenderAPI contact database.
  2. This operation can be used in workflows that need to synchronize contact information between WhatsApp and other CRM systems by using the LID as a reference.

Properties

Name Meaning
Phone Number or JID The phone number or JID (e.g., 212612345678@s.whatsapp.net) for which the LID is to be retrieved. This is a required input.
Session Optional session selection to specify which WhatsApp session to use for the request. If not provided, the session from the incoming item is used automatically.
Retry Failed Requests Whether to retry WasenderAPI requests when the API returns certain error codes (408, 429, 500, 502, or 503).
Max Retries Maximum number of retry attempts after the initial request in case of failure.

Output

JSON

  • json - The JSON response from WasenderAPI containing the LID information corresponding to the provided phone number or JID.

Dependencies

  • WasenderAPI with an API key credential for authentication

Troubleshooting

  • Ensure the phone number or JID is correctly formatted, e.g., including the domain '@s.whatsapp.net'.
  • Verify that the session ID is valid and active if manually specified.
  • If the API returns errors like 408, 429, 500, 502, or 503, the node can retry requests based on the retry settings; adjust these settings if persistent failures occur.
  • Common error messages include missing or invalid session ID, invalid phone number/JID format, or network/API connectivity issues. Check credentials and network access.

Discussion