Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Profile resource and the Update Profile Picture operation, it updates a user's profile picture by setting it to an image located at a specified URL. This is useful in scenarios where you want to programmatically update user avatars or profile images based on external image URLs, such as syncing profile pictures from social media or other platforms.

Example use cases:

  • Automatically updating a user's profile picture after they upload a new photo elsewhere.
  • Syncing profile pictures across multiple systems by providing a URL to the latest image.
  • Bulk updating profile pictures using URLs stored in a database or spreadsheet.

Properties

Name Meaning
Instance Name The name of the instance where the profile picture will be updated.
Image URL The URL of the image that will be set as the new profile picture.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to update the profile picture. The exact structure depends on the API's response but typically includes confirmation of success or details about the updated profile picture.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node uses the base URL https://doc.evolution-api.com/api-reference for API requests.
  • Proper configuration of the API authentication credentials within n8n is necessary.

Troubleshooting

  • Operation not supported error: If the node throws an error stating the operation is not supported, verify that the Resource is set to "Profile" and Operation to "Update Profile Picture".
  • Invalid or missing parameters: Ensure that both "Instance Name" and "Image URL" are provided and valid. Missing or empty values will likely cause API errors.
  • Authentication failures: Confirm that the API key credential is correctly configured and has sufficient permissions.
  • Image URL issues: The URL must point to a publicly accessible image. Private or inaccessible URLs will cause the update to fail.
  • API endpoint changes: Since the base URL points to documentation, ensure the actual API endpoint used internally matches the current Evolution API specification.

Links and References

Discussion