Actions55
- Session Actions
- Message Actions
- Chat Actions
- Contact Actions
- Group Actions
- Webhook Actions
- Status Actions
Overview
This node integrates with the WAHA API to manage WhatsApp contacts and perform various contact-related operations. Specifically, the Get Contacts operation retrieves a list of all contacts associated with a specified WhatsApp session.
Common scenarios where this node is beneficial include:
- Synchronizing WhatsApp contacts with a CRM or database.
- Automating workflows that require access to WhatsApp contact information.
- Building customer support tools that need to fetch contact lists dynamically.
For example, you can use this node to fetch all contacts from a WhatsApp session and then filter or process them in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Session Name | The name of the WhatsApp session to use for the operation. |
| Additional Fields | Optional extra parameters; for Get Contacts, no specific additional fields are used. |
Note: The "Additional Fields" collection includes options like Filename, Mimetype, Limit, etc., but for the Get Contacts operation, only the session name is relevant.
Output
The output JSON contains the response from the WAHA API's /api/contacts endpoint, which returns the list of contacts for the specified WhatsApp session.
Typical structure (example):
{
"contacts": [
{
"id": "contact-id",
"name": "Contact Name",
"number": "phone-number",
"profilePicUrl": "url-to-profile-picture",
"status": "contact status or about info"
// ... other contact details
},
// more contacts...
]
}
The exact fields depend on the WAHA API response but generally include contact identifiers, names, phone numbers, and optionally profile pictures or status messages.
No binary data is output by this operation.
Dependencies
- Requires an active WAHA API credential with a valid base URL and API key.
- Requires a valid WhatsApp session name configured in the credentials or provided as input.
- Also requires a subscription and API key for the n8n Tools API for validation purposes.
- The node makes HTTP requests to the WAHA API endpoints.
Troubleshooting
- Invalid Subscription or API Key: If the n8n Tools API validation fails with 401 or 403 errors, check that your API keys and subscriptions are valid and correctly configured.
- Unknown Contact Operation Error: If an unsupported operation is selected, the node will throw an error indicating the unknown operation.
- Session Not Found or Invalid: Ensure the session name corresponds to an active WhatsApp session in WAHA.
- Network or API Errors: Check network connectivity and WAHA API availability if requests fail.
Links and References
- WAHA API Documentation (replace with actual URL if available)
- WhatsApp Automation Concepts
- n8n Documentation