Actions76
- Message Actions
- Chat Actions
- Contact Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
- Profile Actions
- LID Actions
- File Actions
LID → Get by Phone
AI-generatedOverview
This node interacts with the Wappfy API to perform various WhatsApp-related operations. Specifically, for the LID resource and the Get by Phone operation, it retrieves the Linked ID (LID) associated with a given phone number. This is useful when you have a phone number and want to find its corresponding LID in the Wappfy system.
Common scenarios include:
- Looking up user identifiers linked to phone numbers for messaging or contact management.
- Integrating WhatsApp contact data into CRM or marketing automation workflows.
- Validating or enriching phone number data with additional identifiers.
Example: Given a phone number, the node fetches the LID so that subsequent actions can target the correct WhatsApp user.
Properties
| Name | Meaning |
|---|---|
| Phone Number | Phone number to get LID for |
Output
The output JSON contains the response from the Wappfy API for the LID lookup by phone number. It typically includes details about the LID associated with the provided phone number.
If multiple items are returned, each will be an individual JSON object in the output array.
No binary data output is involved in this operation.
Dependencies
- Requires an active Wappfy API credential with base URL, instance name, and an API key.
- The node makes HTTP requests to the Wappfy API endpoints.
- Proper configuration of the Wappfy API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrectly formatted phone number may result in no data found or errors.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors indicate problems with the API key or instance configuration.
- "Not Found" or empty responses suggest the phone number does not have an associated LID.
- Timeout or connection errors require checking network access to the Wappfy API endpoint.
To resolve errors, verify credentials, ensure the phone number format matches expected input, and confirm network connectivity.
Links and References
- Wappfy API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics