Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API by performing various operations on different resources. Specifically, for the resource "Instancia" and operation "Buscar Instancia," it enables searching for an instance by its name. This is useful in scenarios where you need to retrieve details about a particular instance within the Evolution system, such as fetching configuration or status information based on the instance's name.
Practical examples include:
- Automating retrieval of instance details during workflows that manage multiple instances.
- Integrating instance search functionality into larger automation pipelines to conditionally process data based on instance attributes.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance you want to search for. |
The property "Nome Da Instância" expects a string input representing the exact name of the instance to be fetched.
Output
The node outputs a JSON array containing the results of the instance search. Each item in the array corresponds to an instance matching the search criteria, including all relevant instance details returned by the Evolution API.
If the API supports binary data related to instances (not indicated in the provided code), it would be included accordingly, but this node primarily returns JSON data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node depends on the Evolution API service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure you use valid combinations of resource and operation.
- Authentication errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly set up.
- Empty or no results: If the instance name does not match any existing instance, the output will be an empty array. Double-check the instance name spelling and existence.
- Network or API errors: Connectivity issues or API downtime can cause failures. Check network connectivity and API status.
Links and References
- Evolution API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes