WassengerInstall

Overview

The node interacts with the Wassenger WhatsApp API, specifically supporting multiple resources including Campaigns. For the "Get Campaign" operation under the Campaigns resource, it retrieves detailed information about a specific campaign by its ID. This is useful for users who want to fetch and analyze campaign data such as status, metrics, or configuration within their automation workflows.

Practical examples include:

• Automatically retrieving campaign details after creation to log or process results.
• Fetching campaign info to trigger conditional logic based on campaign status.
• Integrating campaign data into dashboards or reports.

Properties

Output

The node outputs JSON data representing the campaign details fetched from the Wassenger API. The exact structure depends on the API response but typically includes fields such as campaign name, status, start/end dates, message counts, and other metadata related to the campaign.

No binary data output is indicated for this operation.

Dependencies

• Requires an active connection to the Wassenger WhatsApp API.
• Needs an API key credential configured in n8n for authentication.
• The node relies on the executeCampaignOperations method from the campaigns action module to perform the API call.

Troubleshooting

• Common issues:

  • Invalid or missing Campaign ID will cause errors.
  • Authentication failures if the API key is incorrect or expired.
  • Network or API downtime can lead to request failures.

• Error messages:

  • Errors returned from the API (e.g., "Campaign not found") should be checked against the provided Campaign ID.
  • Authentication errors require verifying the API key credential setup.
  • Timeout or connectivity errors suggest checking network access and API availability.

Links and References

• Wassenger API Documentation (general reference for API endpoints and campaign data)
• n8n documentation on API credentials for setting up API keys