Evolution API icon

Evolution API

Interact with Evolution API

Overview

This node interacts with the Evolution API to update the name of a group within a specified instance. It is useful in scenarios where you need to programmatically rename groups, for example, to reflect changes in project names, team structures, or event titles without manual intervention.

Practical examples include:

  • Automatically renaming a project group when the project title changes.
  • Updating group names to maintain consistency across multiple platforms.
  • Managing group names dynamically based on external triggers or workflows.

Properties

Name Meaning
Nombre De La Instancia The name of the instance where the group name will be updated.
ID Del Grupo The unique identifier of the group whose name is to be updated.
Nuevo Nombre Del Grupo The new name that will be assigned to the group.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to update the group's name. This typically includes confirmation of the update or details about the updated group. The exact structure depends on the API's response but generally confirms success or failure of the operation.

No binary data output is expected from this node.

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 in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials can cause authentication failures.
    • Providing an incorrect group ID or instance name may result in errors or no changes.
    • Network connectivity issues can prevent successful API calls.
  • Error Messages:

    • "Operação não suportada." indicates that the requested operation is not supported by the node; ensure the correct resource and operation are selected.
    • API error responses may include messages about invalid parameters or permission issues; verify input values and API permissions.
  • Resolutions:

    • Double-check the API key and ensure it has the required permissions.
    • Verify that the group ID and instance name are correct and exist in the system.
    • Ensure stable network connectivity and that the Evolution API service is reachable.

Links and References

Discussion