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 Pending operation, it retrieves a paginated list of pending WhatsApp chats. This is useful in scenarios where you want to monitor or process chats that are awaiting action or response.

Practical examples include:

  • Fetching pending chats to display in a dashboard for customer support agents.
  • Automating follow-up messages or notifications based on pending chat status.
  • Integrating pending chat data into CRM or ticketing systems for workflow automation.

Properties

Name Meaning
Limit Limit the number of results per page (number). Controls how many pending chats to fetch.
Page Page number for pagination (number). Specifies which page of results to retrieve.

Output

The output is a JSON object containing the list of pending WhatsApp chats retrieved from the Zender API endpoint /get/wa.pending. The structure typically includes chat details such as sender, message content, timestamps, and status indicating they are pending.

The node does not output binary data for this operation.

Example output snippet (conceptual):

{
  "chats": [
    {
      "id": "12345",
      "sender": "+1234567890",
      "message": "Hello, I need help",
      "timestamp": "2024-06-01T12:34:56Z",
      "status": "pending"
    },
    ...
  ],
  "pagination": {
    "limit": 10,
    "page": 1,
    "total": 50
  }
}

Dependencies

  • Requires an API key credential for authenticating with the Zender WhatsApp API.
  • The node uses HTTP GET requests to the Zender API base URL configured in credentials.
  • Pagination parameters (limit and page) are passed as query string parameters.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Requesting a page number beyond available pages may return empty results.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Rate limiting or quota exceeded errors require checking API usage limits with Zender.
    • Unexpected response formats or server errors suggest temporary API issues; retry later.

  • To resolve errors, ensure correct API credentials, valid pagination values, and stable network connection.

Links and References

Discussion