WaAPI icon

WaAPI

Interact with WaAPI API
Join our community

Actions85

Overview

This node interacts with the WaAPI API to retrieve detailed information about a specific message by its unique identifier. It is useful in scenarios where you need to fetch metadata or status of a particular message within a chat system, such as checking delivery status, content details, or message attributes.

For example, you might use this node to:

  • Verify if a sent message was delivered or read.
  • Retrieve message content or metadata for logging or auditing.
  • Integrate message details into other workflows like CRM updates or notifications.

Properties

Name Meaning
Id Instance ID (a numeric identifier) required to specify which instance to query.
Message Id Serialized message identifier string formatted as <fromMe>_<chatId>_<hash>. This uniquely identifies the message to retrieve.

Output

The node outputs JSON data containing detailed information about the requested message. The exact structure depends on the WaAPI response but typically includes fields such as message content, sender info, timestamps, delivery status, and any associated metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the WaAPI service.
  • Needs network access to https://waapi.app/api/v1.
  • The node uses the OpenAPI specification bundled internally to define its properties and requests.

Troubleshooting

  • Invalid or missing API credentials: Ensure that a valid API key credential is configured in n8n for the WaAPI service.
  • Incorrect Message Id format: The Message Id must follow the serialized format <fromMe>_<chatId>_<hash>. Providing an incorrectly formatted ID will likely cause errors or empty responses.
  • Instance ID issues: The numeric Id must correspond to a valid instance; otherwise, the API may return errors or no data.
  • Network or API downtime: Connectivity issues or API service outages can cause request failures. Check network settings and WaAPI service status.

Common error messages might include authentication failures, invalid parameters, or not found errors. Resolving these involves verifying credentials, input formats, and instance existence.

Links and References

Discussion