Evolution API

Overview

The node "Evolution API" allows users to interact with the Evolution API service. Specifically, for the resource Perfil (Profile) and operation Buscar Perfil (Fetch Profile), it enables fetching profile information based on given input parameters such as instance name and contact number. This node is useful in scenarios where you need to retrieve user or business profile details programmatically from the Evolution API, for example, to display profile data in workflows, verify contact information, or integrate profile data into other systems.

Properties

• Nome Da Instância is a required string input where the user specifies the instance name.
• Contato is a required string input representing the contact number related to the profile being fetched.

Output

The node outputs an array of JSON objects containing the profile data retrieved from the Evolution API. Each object corresponds to a profile matching the input criteria. The exact structure depends on the API response but typically includes profile details such as name, contact info, and possibly business or professional profile attributes.

If the API supports binary data (e.g., profile images), this would be included in the output's binary field, but no explicit binary handling is shown in the provided code snippet.

Dependencies

• Requires an API key credential for authenticating requests to the Evolution API.
• The base URL for API requests is https://doc.evolution-api.com/api-reference.
• The node expects JSON responses and sends requests with appropriate headers (Accept: application/json, Content-Type: application/json).
• No additional external dependencies are indicated beyond the Evolution API service and its authentication.

Troubleshooting

• Operation not supported error: If the node throws an error stating the operation is not supported, ensure that the selected resource and operation names exactly match those implemented by the node.
• Missing required parameters: Both "Nome Da Instância" and "Contato" are required. Omitting these will likely cause errors or empty results.
• Authentication issues: Verify that the API key credential is correctly configured and has sufficient permissions.
• API connectivity problems: Check network access to the Evolution API endpoint and confirm the base URL is correct.
• Unexpected API response: If the output is empty or malformed, verify that the contact number and instance name are valid and exist in the Evolution API system.

Links and References

• Evolution API Documentation (official API reference)
• n8n documentation on creating custom nodes