Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" allows users to interact with the Evolution API service. Specifically, for the "Profile" resource and the "Update Profile Name" operation, it enables updating the name of a user profile on the specified instance. This is useful in scenarios where you need to programmatically rename profiles within an application or system managed by the Evolution API, such as automating user management or synchronizing profile data across platforms.
Example use cases:
- Automatically updating profile names based on external data changes.
- Renaming profiles during batch processing or migrations.
- Integrating profile updates into larger workflows that manage user data.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance where the profile exists; required to identify the target environment. |
| Name | The new profile name to set; this is the updated value for the profile's name field. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to update the profile name. The structure of the JSON output depends on the API's response but typically includes confirmation of the update or details about the updated profile. There is no indication that binary data is returned.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - The node expects JSON content-type headers and accepts JSON responses.
- Proper configuration of the API authentication credentials in n8n is necessary.
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 to "profile-api" and "update-profile-name" respectively.
- Authentication errors: Ensure that the API key or authentication token is valid and properly configured in the node credentials.
- Invalid instance name or profile name: Confirm that the instance name exists and the new profile name meets any constraints imposed by the Evolution API.
- Network or API endpoint issues: Check network connectivity and that the base URL has not changed or become unavailable.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on creating custom nodes