Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node interacts with the Wassenger WhatsApp API to retrieve user status information for a specified WhatsApp number. The "Get User Status" operation allows users to fetch statuses published by WhatsApp contacts, filtered and sorted according to various criteria such as message flow direction, delivery status, content type, date ranges, and more.

Practical scenarios include:

  • Monitoring the status updates of specific WhatsApp contacts or groups.
  • Filtering statuses to analyze only inbound or outbound messages.
  • Tracking scheduled statuses that will be published in the future.
  • Searching statuses by text content, media filename, or contact name.
  • Paginating through large sets of status data for reporting or automation workflows.

For example, a marketing team could use this node to gather all image-type statuses sent from a particular WhatsApp number within a date range, helping them analyze customer engagement.

Properties

Name Meaning
WhatsApp Number The ID of the WhatsApp number (device) for which to retrieve user statuses. This is selected from available WhatsApp numbers linked to the account.
Filters A collection of optional filters to narrow down the returned statuses:
- Flow Filter statuses by message direction: "Inbound" (received) or "Outbound" (sent).
- My Status Only Return only statuses published by your own WhatsApp number (boolean).
- Scheduled Only Return only statuses that are scheduled to be published in the future (boolean).
- Delivery Status Filter statuses by delivery acknowledgment status. Options include: "Pending", "Sent", "Delivered", "Read", "Failed".
- WhatsApp IDs Filter statuses by one or multiple WhatsApp IDs (WID).
- Search Search statuses by partial text content, contact name, or media filename.
- Chat ID Filter statuses by chat WhatsApp ID.
- Phone Number Return statuses sent from a given phone number or WhatsApp WID.
- Reference Filter statuses by exact match on the reference field.
- Type Filter statuses by entry kind/type. Options include: "Text", "Image", "Video".
- Begin From Message ID Return newest messages starting from the given message ID.
- End At Message ID Return oldest messages starting from the given message ID.
- Created After Return statuses created after the specified date/time.
- Created Before Return statuses created before the specified date/time.
- Sort Sort statuses by date. Options: "Recent First" (date descending), "Oldest First" (date ascending).
- Results Page Size Number of results per page (pagination size). Default is 20.
- Page Number Page number to return (starting from 0).

Output

The node outputs an array of JSON objects representing user statuses matching the specified filters. Each object contains details about a single status update, including metadata such as:

  • Status content (text, image, video, etc.)
  • Sender information
  • Delivery acknowledgment status
  • Timestamps (creation date, scheduled publish date)
  • Associated chat or contact identifiers
  • Reference fields and other custom metadata

If binary data is included (e.g., images or videos in statuses), it would typically be represented separately in the output's binary property, but this node primarily returns JSON data describing the statuses.

Dependencies

  • Requires an active connection to the Wassenger WhatsApp API via an API key credential configured in n8n.
  • The node depends on the Wassenger API endpoints for user status retrieval.
  • The "WhatsApp Number" property dynamically loads available devices via a method integrated into the node.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key credential can cause authentication failures.
    • Specifying an invalid WhatsApp number (device) ID may result in no data or errors.
    • Using incompatible filter combinations might return empty results.
    • Pagination parameters out of range could lead to empty pages.

  • Error Messages:

    • Authentication errors usually indicate issues with the API key; verify credentials.
    • "No statuses found" indicates filters did not match any records; try broadening filters.
    • Network or API downtime errors require checking Wassenger service status.

  • Resolutions:

    • Ensure the API key credential is correctly set up and has necessary permissions.
    • Validate the WhatsApp number/device ID exists and is active.
    • Adjust filters to less restrictive values to confirm data availability.
    • Check network connectivity and retry if transient errors occur.

Links and References

Discussion