Actions28
- Messages Actions
- Media Actions
- Templates Actions
- Contacts Actions
- Analytics Actions
- Webhooks Actions
Overview
The "Check Multiple Contacts" operation in the WhatsApp Enhanced node allows users to verify the existence or status of multiple WhatsApp contacts by providing a list of phone numbers. This is useful for workflows that need to validate contact information before sending messages, managing contact lists, or performing bulk operations on verified contacts.
Practical examples include:
- Validating a batch of customer phone numbers before launching a marketing campaign.
- Filtering out invalid or non-WhatsApp numbers from a contact list.
- Automating contact verification as part of onboarding or CRM synchronization processes.
Properties
| Name | Meaning |
|---|---|
| Phone Numbers | Comma-separated list of phone numbers to check (e.g., "5511999999999,441632960961"). |
Output
The node outputs JSON data containing the results of the contact checks for each provided phone number. Each item in the output corresponds to one input set and includes the response from the WhatsApp API about the validity or status of the listed contacts.
The exact structure depends on the external WhatsApp API response but typically includes details such as whether each phone number is registered on WhatsApp, their profile information, or error states if any.
No binary data output is produced by this operation.
Dependencies
- Requires an active subscription and valid API key credential for the external N8N Tools API service.
- The node uses the WhatsApp Business API via the N8N Tools API endpoint.
- Proper configuration of credentials within n8n is necessary to authenticate requests.
- Network access to the N8N Tools API endpoint must be available.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly configured and active.
- HTTP Request Failures: Network issues or incorrect API URLs can cause failures. Ensure the API URL is reachable and correct.
- Malformed Phone Numbers: Input phone numbers should be in international format without extra characters. Improper formatting may lead to unexpected results or errors.
- Empty or Missing Phone Numbers: The "Phone Numbers" property is required; leaving it empty will cause the node to fail.
- API Rate Limits: Bulk checking many contacts might hit rate limits imposed by the external API. Consider batching requests or handling errors gracefully.