Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The node interacts with the Zender WhatsApp API to manage WhatsApp chats. Specifically, for the Chat - Get Single operation, it retrieves a single chat message by its ID and type (sent or received). This is useful when you want to fetch detailed information about a specific chat message, such as its content, timestamp, sender/receiver details, and status.

Common scenarios:

  • Fetching details of a particular sent or received WhatsApp message for auditing or logging.
  • Retrieving a chat message to display in a dashboard or user interface.
  • Using the chat data for further processing or integration with other systems.

Example:
You have a chat ID from a previous workflow step and want to get the full details of that chat message to analyze or store it elsewhere.

Properties

Name Meaning
Chat ID The unique identifier of the chat message to retrieve.
Chat Type Specifies whether to retrieve a "Sent" or "Received" chat message. Options: sent, received.

Output

The output is a JSON object containing the details of the requested chat message. The exact structure depends on the API response but typically includes fields such as:

  • Message ID
  • Sender and receiver information
  • Message content
  • Timestamp
  • Status and metadata related to the chat message

The node does not output binary data for this operation.

Dependencies

  • Requires an active connection to the Zender WhatsApp API.
  • Needs an API key credential configured in n8n for authentication.
  • The base URL and secret API key are used to authenticate and make requests to the Zender API endpoints.

Troubleshooting

  • Invalid Chat ID: If the provided chat ID does not exist or is incorrect, the API may return an error or empty result. Verify the chat ID before making the request.
  • Incorrect Chat Type: Ensure the chat type matches the actual message type (sent or received). Mismatched types may cause no data to be returned.
  • Authentication Errors: Make sure the API key credential is valid and has the necessary permissions.
  • API Rate Limits: Excessive requests might lead to rate limiting; handle errors gracefully and consider retry logic.
  • Network Issues: Connectivity problems can cause request failures; verify network access to the Zender API endpoint.

If the node throws an error, check the error message for clues, and ensure all required parameters are correctly set.

Links and References

Discussion