Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the resource Perfil and operation Atualizar Nome Do Perfil, it updates the name of a user profile instance. This is useful in scenarios where you need to programmatically rename profiles within the Evolution system, such as automating profile management or synchronizing profile names from other systems.
For example, if you have multiple user profiles and want to update their display names based on external data or events, this node can perform that update efficiently.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to identify which profile to update. This is a required string input. |
| Nome | The new name to assign to the profile. This is a required string input representing the updated profile name. |
Output
The node outputs a JSON array containing the result of the update operation. Each item in the output corresponds to the response from the Evolution API after attempting to update the profile name. The exact structure depends on the API response but generally includes confirmation of the update or details about the updated profile.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API endpoint to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Operation not supported error: If you receive an error stating the operation is not supported, verify that the resource is set to "profile-api" and the operation to "update-profile-name". These must match exactly.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to update profile names.
- Missing required properties: Both "Nome Da Instância" and "Nome" must be provided; otherwise, the node will fail.
- API connectivity issues: Check network access to the Evolution API endpoint and confirm no firewall or proxy blocks exist.
Links and References
- Evolution API official documentation (please refer to your internal or vendor-provided API docs for detailed endpoints and payloads).
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/creating-nodes/
- General REST API usage best practices.