Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node named "Evolution API" allows users to interact with the Evolution API service. Specifically, for the resource "Instancia" and operation "Buscar Instancia" (Fetch Instance), 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 API system, such as fetching configuration or status information based on the instance's name.
Practical examples include:
- Automating retrieval of instance details for monitoring or reporting.
- Integrating instance data into workflows that require dynamic access to specific instances.
- Searching for instances before performing further operations like updates or deletions.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance you want to search for. Enter the exact instance name string. |
Output
The node outputs a JSON array containing the data returned from the Evolution API for the searched instance(s). Each item in the array represents an instance matching the search criteria, including all relevant instance details as provided by the API.
If the API returns binary data related to the instance (not indicated in the code), it would be included accordingly, but based on the static analysis, the output is primarily JSON structured data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is set to
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).
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 Issues: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
- Empty or Incorrect Instance Name: Providing an empty or incorrect instance name may result in no data found or errors from the API. Double-check the instance name input.
- Network or API Errors: Connectivity issues or API downtime can cause request failures. Check network connectivity and API status.
Links and References
- Evolution API Documentation (official API reference site)