Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the provided Resource "Instance" and Operation "Connect Instance," it enables connecting to a specified instance by its name. This is useful in scenarios where you need to programmatically establish connections to different instances managed via the Evolution API, such as automating workflows that depend on instance-specific data or actions.
Practical examples include:
- Connecting to a particular instance to retrieve or update its configuration.
- Automating instance management tasks within larger automation workflows.
- Integrating instance connection steps into multi-step processes requiring dynamic instance selection.
Properties
| Name | Meaning |
|---|---|
| Instance Name | Enter the name of the instance you want to search |
The property "Instance Name" is a required string input where the user specifies the exact name of the instance they want to connect to.
Output
The node outputs JSON data representing the result of the "Connect Instance" operation. The output structure is an array of JSON objects returned from the Evolution API corresponding to the connection attempt or instance details retrieved.
No binary data output is indicated in the source code.
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 depends on the Evolution API being accessible and the provided instance name being valid.
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 implemented.
- Invalid instance name: Providing an incorrect or non-existent instance name may cause the API call to fail or return empty results. Ensure the instance name matches exactly.
- Authentication issues: Failure to provide valid API credentials will prevent successful connection.
- Network errors: Connectivity problems to the Evolution API endpoint can cause execution failures.
Links and References
- Evolution API Documentation (as referenced in the node's base URL)