Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

The node "Evolution API Direct" allows users to interact directly with the Evolution API by specifying a resource and operation, along with necessary parameters such as server URL and API key. Specifically, for the resource Perfil (Profile) and operation Atualizar Status (Update Status), this node updates the status message of a profile instance in the Evolution system.

This node is beneficial when you want to programmatically update profile statuses within your Evolution API environment, for example:

  • Automatically setting a user's availability or status message based on external triggers.
  • Integrating status updates into workflows that manage user profiles dynamically.

Properties

Name Meaning
Server URL The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API.
Nome Da Instância The name of the specific Evolution API instance where the profile status will be updated.
Status The new status message for the profile, limited to a maximum of 139 characters.

Output

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

No binary data output is indicated.

Dependencies

  • Requires access to an Evolution API server reachable via the provided Server URL.
  • Requires a valid API key credential for authentication.
  • The node expects the Evolution API instance name to target the correct profile context.

Troubleshooting

  • Unsupported Operation Error: If the specified resource-operation combination is not supported, the node throws an error stating the operation is unsupported. Ensure the resource is "profile-api" and the operation is "update-profile-status".
  • Authentication Failures: Incorrect or missing API key will cause authentication errors. Verify the API key is correct and has sufficient permissions.
  • Invalid Server URL: Providing an incorrect or unreachable Server URL will result in connection errors. Confirm the URL is correct and accessible.
  • Status Length Exceeded: The status message must not exceed 139 characters; longer messages may cause validation errors.
  • Instance Name Missing: The instance name is required; omitting it will prevent the node from targeting the correct profile.

Links and References

Discussion