Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

This node integrates with the Evolution API to manage WhatsApp groups and other related resources. Specifically, the "Group" resource with the "Promote Admin" operation allows you to promote a participant in a WhatsApp group to an admin role. This is useful for automating group management tasks such as delegating administrative privileges without manual intervention.

Practical scenarios include:

  • Automatically promoting trusted members to admins when they join a group.
  • Managing group roles dynamically based on external triggers or workflows.
  • Streamlining group administration in large communities or teams.

Properties

Name Meaning
Group ID The unique identifier of the WhatsApp group where the participant will be promoted.
Additional Fields Optional extra parameters including:
- Delay: Time in milliseconds to wait before sending the request.
- Link Preview: Enable or disable link previews in messages (true/false).
- Quoted Message ID: ID of a message to quote or reply to.
- Mentions: Comma-separated list of phone numbers to mention in the message.

Output

The node outputs JSON data representing the response from the Evolution API after attempting to promote a participant to admin in the specified WhatsApp group. The exact structure depends on the API response but typically includes confirmation of the action or error details.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for the Evolution API to authenticate requests.
  • Optionally uses another API key credential for a validation service to verify subscription and API key validity before making the main request.
  • The node expects configuration of instance name and base URL for the Evolution API.
  • Network access to the Evolution API endpoints is necessary.

Troubleshooting

  • Invalid Subscription or API Key: If the validation step fails with 401 or 403 status codes, check that the provided API keys are correct and active.
  • Unknown Operation or Resource Errors: These occur if the node parameters specify unsupported operations or resources; ensure the "Resource" is set to "Group" and "Operation" to "Promote Admin".
  • API Request Failures: Network issues or incorrect group IDs can cause errors. Verify the group ID is valid and the instance is properly connected.
  • Delay Parameter Misuse: Setting an excessively high delay may cause unexpected workflow timing issues.

Links and References

Discussion