Wazend API

Overview

The node named "Wazend API" is designed to interact with the Wazend API, providing various operations grouped by resources. Specifically, for the resource Perfil (Profile) and operation Buscar Perfil Profesional (Fetch Professional Profile), it allows users to retrieve professional profile information associated with a given contact number within a specified instance.

This node is beneficial in scenarios where automation workflows need to fetch detailed professional profile data from the Wazend platform, such as integrating contact management systems, enriching CRM records, or automating customer support processes that require up-to-date profile information.

Example use cases:

• Automatically retrieving a professional profile when a new contact message arrives.
• Enriching lead data with professional details before passing it to sales teams.
• Verifying contact profiles during automated outreach campaigns.

Properties

Output

The node outputs a JSON array containing the fetched professional profile data corresponding to the provided contact number within the specified instance. The structure of the JSON output depends on the Wazend API response for the professional profile but generally includes profile details such as name, business information, and other relevant professional attributes.

If the node supports binary data output, it would typically represent media or documents related to the profile; however, based on the provided code and properties, the primary output is JSON-formatted profile data.

Dependencies

• Requires an active connection to the Wazend API endpoint at https://docs.wazend.net/wazend.
• Needs an API authentication credential configured in n8n to authorize requests to the Wazend API.
• The node depends on the internal helper functions mapped under resourceOperationsFunctions to execute the specific resource-operation logic.

Troubleshooting

• Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set and that the implementation supports them.
• Authentication Failures: Ensure the API key or authentication token is valid and properly configured in n8n credentials.
• Invalid Contact Number: Providing an incorrect or improperly formatted contact number may result in empty or error responses.
• Instance Name Issues: The instance name must match exactly the configured Wazend instance; otherwise, the API call may fail or return no data.

Links and References

• Wazend API Documentation – Official API documentation for reference on endpoints and data structures.
• n8n Documentation on Creating Custom Nodes – For understanding how to extend and customize nodes.