Zender icon

Zender

Interact with Zender WhatsApp API

Overview

The "Create Contact" operation of the Zender node allows users to add a new contact to their Zender WhatsApp contact list. This operation is useful for managing contacts within the Zender platform, enabling automation workflows that involve adding new phone numbers with associated names and optionally assigning them to specific groups.

Practical examples include:

  • Automatically adding new customer phone numbers collected from a web form into the WhatsApp contact list.
  • Organizing contacts by assigning them to groups for targeted messaging campaigns.
  • Integrating CRM systems with WhatsApp contact management via automated workflows.

Properties

Name Meaning
Phone Number The phone number of the contact to create (required).
Contact Name The name of the contact to create (required).
Groups Optional comma-separated list of group IDs to assign the contact to.

Output

The output is a JSON object representing the response from the Zender API after attempting to create the contact. It typically contains details about the newly created contact or an error message if the creation failed.

Example structure (simplified):

{
  "success": true,
  "contactId": "12345",
  "phone": "+1234567890",
  "name": "John Doe",
  "groups": ["group1", "group2"]
}

If the operation fails, the output JSON will contain an error message describing the issue.

Dependencies

  • Requires an API key credential for authenticating with the Zender WhatsApp API.
  • The node uses HTTP POST requests with URL-encoded form data to communicate with the Zender API endpoint /create/contact.
  • No binary data handling is involved in this operation.

Troubleshooting

  • Common issues:

    • Missing required fields such as phone number or contact name will cause the API request to fail.
    • Invalid phone number format may result in errors from the API.
    • Incorrect or missing API credentials will prevent successful communication with the Zender API.
  • Error messages:

    • Errors returned from the API are passed through in the output JSON under an error field.
    • If the node is configured to continue on failure, errors for individual items will be included in the output without stopping the entire workflow.
    • To resolve errors, verify that all required properties are correctly set and that the API key credential is valid.

Links and References

Discussion