Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API Direct," allows users to interact directly with the Evolution API by specifying a resource and operation. In the context of the provided Resource "Perfil" and Operation "Buscar Configurações De Privacidade" (Search Privacy Settings), the node fetches privacy configuration data related to a user profile from the Evolution API.
Typical use cases include:
- Retrieving privacy settings for user profiles in an application that integrates with the Evolution platform.
- Automating workflows that require checking or auditing user privacy configurations.
- Synchronizing privacy settings between Evolution API and other systems.
For example, a marketing automation workflow might use this node to fetch privacy preferences before sending communications, ensuring compliance with user consent.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API instance (e.g., https://api.exemplo.com). |
| API Key | The API key credential used to authenticate requests to the Evolution API. |
| Nome Da Instância | The name of the specific Evolution API instance you want to target. |
Output
The node outputs a JSON array where each item contains the privacy configuration details retrieved from the Evolution API for the specified profile. The exact structure depends on the API response but typically includes fields representing various privacy settings.
No binary data output is indicated or expected.
Dependencies
- Requires access to the Evolution API endpoint specified by the "Server URL".
- Requires a valid API key credential for authentication.
- The node expects the "Nome Da Instância" property to identify the targeted instance within the Evolution API environment.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the selected resource and operation names are correct and implemented in the node.
- Authentication errors: Ensure the API key is valid and has sufficient permissions to access the requested resource.
- Network issues: Confirm that the "Server URL" is reachable from the n8n environment and that there are no firewall or proxy restrictions.
- Missing required properties: Make sure all required input properties ("Server URL", "API Key", and "Nome Da Instância") are provided and correctly formatted.
Links and References
- Evolution API Documentation: https://doc.evolution-api.com/api-reference (as referenced in the code's default base URL)