Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Resource "Instance" and Operation "Fetch Instance," it enables fetching details about a particular instance by its name. This is useful in scenarios where you need to retrieve information about specific instances managed or tracked by the Evolution API, such as monitoring instance status, configuration, or metadata.
Practical examples include:
- Fetching an instance's details before performing further automation steps.
- Validating if an instance exists by querying it by name.
- Integrating instance data into workflows for reporting or alerting purposes.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance you want to search for. Enter the exact instance name here. |
Output
The node outputs a JSON array containing the fetched instance data. Each item in the array represents an instance object with its associated properties as returned by the Evolution API. The structure depends on the API response but typically includes instance identifiers, names, statuses, and other relevant metadata.
If the node supports binary data output, it would be related to any files or attachments associated with the instance, but based on the provided code and properties, only JSON data output is expected.
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. - Proper configuration of the API authentication credentials within n8n is necessary.
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 that the resource is set to "instances-api" and the operation to "fetch-instances".
- Empty or incorrect instance name: Providing an empty or wrong instance name will likely result in no data found or an error from the API. Double-check the instance name input.
- 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 configured.
- Network issues: Connectivity problems to the Evolution API endpoint can cause request failures. Check network access and proxy settings if applicable.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on API Credentials for setting up authentication tokens