WassengerInstall

Overview

The "Update Message" operation under the "Outbound Messages" resource allows users to modify existing outbound WhatsApp messages. This node is useful when you need to change message content, update delivery details, or adjust metadata after a message has been created but before it is sent or processed further.

Common scenarios include:

• Correcting or updating the text of a scheduled message.
• Changing the target recipient phone number, group, chat, or channel.
• Rescheduling the delivery time of a message.
• Adjusting message priority or assigning it to a different agent or device.
• Removing specific fields such as media or location data from the message.
• Adding custom labels for categorization or tracking purposes.

Practical example: Suppose you scheduled a promotional message to be sent to a customer group but realized the message text contains a typo. Using this node, you can update the message text and reschedule the delivery without creating a new message.

Properties

Output

The node outputs an array of JSON objects representing the updated outbound message(s). Each output item contains the updated message data reflecting the changes made through the input properties.

If the message includes any binary data (such as media files), those would typically be handled separately; however, this operation focuses on updating message metadata and content rather than directly outputting binary data.

Dependencies

• Requires an API key credential for authenticating with the Wassenger WhatsApp API.
• The node depends on dynamic loading methods to fetch options for devices, groups, agents, and labels, which implies connectivity to the Wassenger service to retrieve these lists.
• Proper configuration of the Wassenger API credentials within n8n is necessary.

Troubleshooting

• Invalid Message ID: If the provided Message ID does not exist or is malformed, the node will likely throw an error indicating the message could not be found. Verify the Message ID is correct.
• Invalid Phone Number Format: Phone numbers must be in E.164 format (e.g., +1234567890). Providing an incorrectly formatted number may cause validation errors.
• Missing Required Fields: The Message ID is required. Omitting it will prevent the update operation.
• Permission Issues: Ensure the API key used has sufficient permissions to update outbound messages.
• Dependency Loading Failures: If dynamic option loading for devices, groups, agents, or labels fails, check network connectivity and API access.
• Field Removal Conflicts: Attempting to remove fields that do not exist or are mandatory might result in errors.

To resolve errors, verify all inputs, ensure proper API credentials, and confirm that dependent resources (devices, groups, etc.) exist and are accessible.

Links and References

• Wassenger Official API Documentation (for detailed API capabilities and field definitions)
• E.164 Phone Number Formatting
• n8n Documentation on Creating Custom Nodes