whapi

Overview

This node is designed to retrieve a specific message by its ID from a messaging service. It is useful in scenarios where you need to fetch detailed information about a particular message, such as for auditing, displaying message content, or processing message metadata. For example, you might use this node to get the status or content of a message sent through a communication channel.

Properties

Output

The output will contain a JSON object representing the details of the requested message. This typically includes message content, sender and recipient information, timestamps, and status data. If the node supports binary data (e.g., attachments), it would be included accordingly, but based on the provided code, only JSON message data is expected.

Dependencies

• Requires an API key or access token credential to authenticate requests.
• Depends on an external messaging API accessible via the configured authentication.
• The node internally uses a router module to handle the operation logic.

Troubleshooting

• Common issues:

  • Invalid or missing MessageID: Ensure the MessageID property is correctly set and corresponds to an existing message.
  • Authentication errors: Verify that the access token is valid and has sufficient permissions.
  • Network or API errors: Check connectivity and API availability.

• Error messages:

  • "Message not found": The specified MessageID does not exist or is inaccessible.
  • "Unauthorized": Authentication failed due to invalid credentials.
  • "Request timeout" or similar network errors: Retry or check network settings.

Links and References

• Refer to the messaging service's official API documentation for details on message retrieval endpoints and required parameters.
• n8n documentation on creating and using custom nodes for API integrations.