Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The node integrates with the Zender WhatsApp API to manage and interact with WhatsApp campaigns. Specifically, for the Campaign - Start operation, it allows users to start a WhatsApp campaign by triggering the campaign's chat sending process remotely.

This operation is useful in scenarios where you have pre-configured WhatsApp campaigns and want to programmatically initiate them from an automation workflow. For example, after preparing a marketing campaign with targeted messages, you can use this node to start sending those messages to the intended recipients automatically.

Practical examples:

  • Starting a promotional WhatsApp campaign to notify customers about a sale.
  • Initiating a customer engagement campaign that sends scheduled messages.
  • Automating the launch of a notification campaign after certain triggers in your system.

Properties

Name Meaning
Campaign ID The unique numeric identifier of the WhatsApp campaign to start. Required for this operation.

Output

The output is a JSON object containing the response from the Zender API after attempting to start the specified campaign. This typically includes status information about the campaign start request, such as success confirmation or error details.

The output structure is:

{
  "json": {
    // API response fields indicating campaign start status
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Zender WhatsApp API via an API key credential.
  • The node uses HTTP GET requests authenticated with the provided API secret and base URL configured in the credentials.
  • No additional environment variables are required beyond the API credential setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Campaign ID: Ensure the Campaign ID is correct and corresponds to an existing campaign in your Zender account.
    • Authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
    • Network or connectivity problems: Confirm that the n8n instance can reach the Zender API endpoint.

  • Error messages:

    • Errors returned from the API will be included in the node output if "Continue On Fail" is enabled.
    • Typical errors include unauthorized access, invalid campaign ID, or server errors.
    • To resolve, check credentials, campaign existence, and API service status.

Links and References

Discussion