Zender icon

Zender

Interact with Zender WhatsApp API
Join our community

Actions42

Overview

The node integrates with the Zender WhatsApp API, enabling automation of various WhatsApp-related tasks. Specifically for the Account - Link operation, it initiates the process to link a new WhatsApp account to the system by requesting a linking URL or token from the API. This is useful when you want to programmatically add new WhatsApp accounts to your Zender setup without manual intervention.

Typical scenarios include:

  • Automating onboarding of new WhatsApp accounts in bulk.
  • Integrating WhatsApp account linking into larger workflows that manage communication channels.
  • Dynamically selecting or specifying a WhatsApp server during account linking.

Example: You can use this node operation to start linking a new WhatsApp account on a specific server (or let the system choose the best available server), then proceed to retrieve QR code info and image for scanning.

Properties

Name Meaning
Additional Fields Optional extra parameters for linking the account. Currently supports:
  Server ID Numeric ID of the WhatsApp server to use for linking. If omitted, the system automatically selects the best available server.

Output

The output JSON contains the response from the Zender API endpoint that initiates the WhatsApp account linking process. This typically includes data such as:

  • A unique token or identifier for the linking session.
  • Possibly a URL or instructions to complete the linking (e.g., scanning a QR code).
  • Status or metadata about the linking request.

This output can be used in subsequent steps to fetch QR code information or monitor the linking status.

Dependencies

  • Requires an API key credential for authenticating with the Zender WhatsApp API.
  • The node uses HTTP GET requests to the Zender API base URL configured in credentials.
  • No additional external dependencies beyond the Zender API and n8n's HTTP request helper.

Troubleshooting

  • Common issues:

    • Missing or invalid API key credential will cause authentication failures.
    • Providing an invalid Server ID may result in errors or fallback to default server selection.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Authentication errors usually indicate problems with the API key or credential configuration.
    • API response errors may include messages about invalid parameters or server unavailability.

  • Resolution tips:

    • Verify the API key credential is correctly set up in n8n.
    • Ensure the Server ID (if provided) corresponds to a valid and active WhatsApp server.
    • Check network access to the Zender API endpoints.
    • Use the "continue on fail" option in n8n to handle errors gracefully in workflows.

Links and References

Discussion