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 resource and Get Received operation, it retrieves a paginated list of received WhatsApp chat messages. This is useful for scenarios where you want to monitor incoming messages, automate responses, or analyze customer interactions.

Practical examples include:

  • Fetching recent received WhatsApp messages to trigger workflows based on customer inquiries.
  • Archiving or processing incoming chats for customer support automation.
  • Integrating received chat data into CRM or analytics platforms.

Properties

Name Meaning
Limit Limits the number of received chat results returned per page. Default is 10.
Page Specifies the page number for pagination through received chat results. Default is 1.

Output

The output is an array of JSON objects representing the received WhatsApp chats fetched from the Zender API endpoint /get/wa.received. Each item corresponds to one received chat message or a batch of messages depending on the API response structure.

The exact structure depends on the Zender API but typically includes details such as:

  • Message ID
  • Sender information
  • Message content
  • Timestamp
  • Status or metadata related to the chat

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Zender WhatsApp API.
  • Needs an API key credential (referred generically as "an API key credential") configured in n8n for authentication.
  • The base URL for the Zender API must be set in the credentials.
  • Uses HTTP GET requests with query parameters limit and page for pagination.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Exceeding rate limits imposed by the Zender API may result in errors or throttling.
    • Providing invalid pagination parameters (e.g., negative numbers) might cause unexpected results or errors.

  • Error messages:

    • Authentication errors usually indicate problems with the API key or credential setup.
    • Network or timeout errors suggest connectivity issues with the Zender API endpoint.
    • API errors with descriptive messages should be checked against Zender API documentation for resolution.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Ensure the limit and page values are positive integers.
    • Check network connectivity and firewall settings if requests fail.
    • Review Zender API status and limits if persistent errors occur.

Links and References

Discussion