Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node interacts with the Wassenger WhatsApp API to update metadata associated with a specific chat contact on a given WhatsApp number. It allows users to add or modify key-value pairs of metadata for contacts, which can be useful for organizing, tagging, or storing additional information about contacts within WhatsApp conversations.
Common scenarios:
- Adding custom tags or notes to contacts for segmentation or follow-up.
- Storing customer preferences or statuses as metadata.
- Updating contact details dynamically based on interactions or external data sources.
Practical example:
A support team might use this node to update a contact's metadata with the current ticket status or priority level after each interaction, enabling better tracking and automation downstream.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) where the contact exists. Options are loaded dynamically. |
| Contact ID | The unique identifier of the contact in WhatsApp (e.g., 447362053576@c.us). |
| Metadata | One or more key-value pairs representing metadata to set or update for the contact. Keys must be alphanumeric or underscores; values can be up to 300 characters. |
Output
The node outputs JSON data representing the result of the metadata update operation for the specified contact. This typically includes confirmation of the updated metadata or the updated contact object as returned by the Wassenger API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured.
- The "WhatsApp Number" property relies on a dynamic options loader method to fetch available devices linked to the user's account.
Troubleshooting
Common issues:
- Invalid or missing WhatsApp Number or Contact ID will cause the operation to fail.
- Metadata keys containing invalid characters or values exceeding length limits may be rejected by the API.
- Network or authentication errors if the API key is incorrect or the Wassenger service is unreachable.
Error messages:
- Errors related to missing required parameters indicate that either the WhatsApp Number or Contact ID was not provided.
- API errors about invalid metadata format suggest checking the key/value constraints.
- Authentication failures require verifying the API key credential setup.
To resolve these, ensure all required fields are correctly filled, metadata keys/values conform to restrictions, and the API key is valid and active.
Links and References
- Wassenger Official API Documentation (for detailed API capabilities and metadata usage)
- n8n Documentation on Creating Custom Nodes