Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node integrates with the Wassenger WhatsApp API to manage chat contacts, specifically allowing you to upsert (update or insert) metadata for a contact associated with a WhatsApp number. This operation is useful when you want to enrich or maintain additional information about your WhatsApp contacts in an automated workflow.

Common scenarios include:

  • Adding custom tags or notes to contacts for segmentation or personalized messaging.
  • Updating contact attributes dynamically based on interactions or external data sources.
  • Synchronizing contact metadata from CRM or other systems into WhatsApp contacts.

For example, you could use this node to add a "customer_status" metadata key with values like "premium" or "trial" to tailor subsequent communications.

Properties

Name Meaning
WhatsApp Number The ID of the WhatsApp number (device) to which the contact belongs.
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 be added or updated for the contact.

The Metadata property supports multiple entries, each consisting of:

  • Key: An alphanumeric string (including underscores) that identifies the metadata field.
  • Value: A string value up to 300 characters representing the metadata content.

Output

The node outputs JSON objects representing the result of the upsert operation for each input item. Each output JSON typically contains the response from the Wassenger API confirming the metadata update or insertion for the specified contact.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message under the error key.

No binary data output is produced by this node.

Dependencies

  • Requires an active Wassenger WhatsApp API account.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The node depends on the Wassenger API endpoints for managing chat contacts and their metadata.

Troubleshooting

  • Invalid Contact ID: If the contact ID does not exist or is malformed, the API may return an error. Verify the contact ID format (e.g., 447362053576@c.us) and ensure the contact exists.
  • Invalid Metadata Key/Value: Metadata keys must be alphanumeric or underscore characters only; values are limited to 300 characters. Violating these constraints can cause errors.
  • Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • API Rate Limits: Excessive requests might lead to rate limiting; consider adding delays or batching inputs.
  • Network Issues: Connectivity problems can cause request failures; verify network access to the Wassenger API.

Links and References

Discussion