Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node interacts with the Wassenger WhatsApp API to retrieve campaign data based on various filter criteria. It is useful for users who want to programmatically query and analyze WhatsApp campaigns managed via Wassenger, such as marketing or notification campaigns.

Typical use cases include:

  • Fetching campaigns created within a specific date range.
  • Filtering campaigns by status (e.g., completed, failed).
  • Retrieving campaigns associated with particular devices, owners, or recipient groups.
  • Paginating through large sets of campaigns with sorting options.

For example, a user might want to get all completed campaigns sent after January 1, 2024, sorted by most recent first, to generate performance reports.

Properties

Name Meaning
Filters A collection of filters to narrow down the campaigns retrieved. Options include:
- Before Date Filter campaigns created before this date (date-time).
- After Date Filter campaigns created after this date (date-time).
- Status Filter by campaign status. Possible values: Draft, Pending, Processing, Completed, Failed, Stopped, Paused, Incomplete.
- Device IDs Filter by one or more WhatsApp device IDs.
- Owner User IDs Filter by one or more owner user IDs.
- Campaign IDs Filter by one or more specific campaign IDs.
- Phone Numbers Filter campaigns by recipient phone numbers (e.g., +447362053576).
- Group IDs Filter campaigns by recipient group chats (e.g., 44736205357600000000@g.us).
- Results Page Size Number of results per page (default 20).
- Page Number Page number to retrieve, starting from 0 (default 0).
- Sort Sort order for results. Options: Recent First (date:desc), Oldest First (date:asc).

Output

The node outputs an array of JSON objects representing campaigns matching the specified filters. Each object contains details about a campaign as returned by the Wassenger API. The exact structure depends on the API response but typically includes fields like campaign ID, creation date, status, associated device and owner IDs, recipient information, and other metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Wassenger WhatsApp API account.
  • Requires an API key credential configured in n8n for authentication with the Wassenger API.
  • The node relies on the Wassenger API endpoints related to campaigns.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Using invalid filter values (e.g., malformed dates or unknown status) may result in API errors.
    • Requesting pages beyond available data may return empty results.

  • Error messages:

    • Authentication errors: Check that the API key credential is correctly set up and valid.
    • Validation errors: Verify that filter inputs conform to expected formats (dates, IDs).
    • Network or API downtime: Ensure network connectivity and that the Wassenger API service is operational.

Links and References

Discussion