Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The node interacts with the Zender WhatsApp API to manage WhatsApp campaigns, messages, contacts, accounts, chats, OTPs, SMS, groups, servers, and phone number validations. Specifically for the Campaign - Stop operation, it stops an active WhatsApp campaign by sending a request to the Zender API to halt message dispatching or other campaign activities.

This node is beneficial in scenarios where you need to programmatically control marketing or notification campaigns on WhatsApp, such as pausing or stopping campaigns based on external triggers or workflow conditions.

Example use case:
You have a WhatsApp marketing campaign running and want to stop it automatically when a certain sales target is reached or when a promotional period ends. Using this node's "Stop Campaign" operation, you can integrate that logic into your automation workflows.

Properties

Name Meaning
Campaign ID The unique numeric identifier of the WhatsApp campaign to stop.

Output

The output is a JSON object containing the response from the Zender API after attempting to stop the specified campaign. This typically includes status information about the success or failure of the stop request.

Example output structure (simplified):

{
  "status": "success",
  "message": "Campaign stopped successfully",
  "campaignId": 123
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Zender WhatsApp API.
  • The node uses HTTP GET requests to the Zender API endpoints.
  • The base URL and API secret are obtained from the configured credentials.
  • No additional environment variables are required beyond the API credential setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Campaign ID: Ensure the Campaign ID provided exists and is correct.
    • Authentication errors: Verify that the API key credential is valid and has necessary permissions.
    • Network or connectivity problems: Confirm that the n8n instance can reach the Zender API endpoint.
    • Campaign already stopped or does not exist: The API may return an error if trying to stop a non-active or non-existent campaign.

  • Error messages:

    • "error": "Invalid campaign ID": Check the Campaign ID input.
    • "error": "Authentication failed": Recheck API key credentials.
    • "error": "Campaign not found": Confirm the campaign exists in Zender.
    • "error": "Failed to stop campaign": Could be due to internal API issues or invalid state; retry or contact support.

If the node is set to continue on fail, errors will be returned in the output JSON under an error field.

Links and References

Discussion