Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to retrieve the profile picture URL of a specified contact. It is useful in scenarios where you need to programmatically access or display the profile image associated with a contact in WhatsApp-like environments, such as customer support dashboards, CRM integrations, or messaging automation workflows.
For example, you might use this node to fetch and show a user's profile picture in a chat interface or to verify contact identities by displaying their profile images.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a numeric identifier for the specific WaAPI instance to target). |
| Contact Id | The unique identifier of the contact whose profile picture URL you want to retrieve. Must include suffixes like @c.us for contacts, @g.us for groups, or @newsletter for newsletters. |
Output
The node outputs JSON data containing the profile picture URL of the specified contact. This URL can be used directly to display or download the profile image.
If the node supports binary data output (not explicitly shown in the provided code), it would typically represent the actual image file fetched from the URL. However, based on the static analysis, the primary output is the JSON field with the profile picture URL.
Dependencies
- Requires an active connection to the WaAPI API service.
- Needs an API key credential configured in n8n to authenticate requests to WaAPI.
- The base URL for API requests is
https://waapi.app/api/v1. - The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or malformed Contact Id (missing suffix or wrong format) may result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; reconfigure the API credential in n8n.
- "Contact not found" or similar errors suggest the Contact Id does not exist or is incorrectly formatted.
- Timeout or network errors require checking your internet connection or API service status.
Links and References
- WaAPI Official Website
- WaAPI API Documentation (for detailed API endpoints and usage)
- n8n Documentation on Creating Custom Nodes