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 service. Specifically, for the resource "Perfil" and operation "Buscar Configurações De Privacidade" (Search Privacy Settings), it retrieves privacy configuration data related to a user profile or instance. This can be useful in scenarios where you need to programmatically access or audit privacy settings of profiles managed within the Evolution API system.
Practical examples include:
- Automatically fetching privacy settings to verify compliance.
- Integrating privacy configurations into dashboards or reports.
- Triggering workflows based on specific privacy setting values.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to query. This is a required string input where you specify which instance's privacy settings you want to retrieve. |
Output
The node outputs JSON data representing the privacy settings retrieved from the Evolution API for the specified instance. The exact structure depends on the API response but generally includes fields describing various privacy options configured for that profile instance.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON.
Dependencies
- Requires an API key credential for authenticating with the Evolution API service.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference. - Proper configuration of the API authentication credentials in n8n is necessary for successful execution.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error stating the operation is not supported. Ensure you use valid combinations of resource and operation.
- Missing Required Property: The "Nome Da Instância" property is required. Omitting it will likely cause errors or empty responses.
- Authentication Issues: Failure to provide valid API credentials will result in authorization errors.
- API Endpoint Changes: Since the base URL points to a documentation URL, ensure the actual API endpoint URLs are correctly configured if different.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n Documentation on Creating Custom Nodes