Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

This node integrates with the Evolution API to automate WhatsApp instance management and messaging tasks. Specifically, the Disconnect Instance operation under the Instance resource allows users to disconnect a WhatsApp instance from the Evolution API service.

Typical use cases include:

  • Automating the disconnection of WhatsApp instances when they are no longer needed.
  • Managing multiple WhatsApp instances programmatically within workflows.
  • Ensuring clean shutdown or reset of WhatsApp connections in automation pipelines.

For example, after completing a batch of message sends, a workflow could disconnect the instance to free up resources or prepare for a new connection.

Properties

Name Meaning
Additional Fields Optional extra parameters:
- Delay: Delay in milliseconds before sending.
- Link Preview: Enable or disable link preview in messages.
- Quoted Message ID: ID of a message to quote or reply to.
- Mentions: Comma-separated list of phone numbers to mention in the message.

Note: For the Disconnect Instance operation, the node primarily uses the instance name credential internally; no additional required input properties are exposed for this operation beyond optional "Additional Fields".

Output

The node outputs JSON data representing the response from the Evolution API after attempting to disconnect the instance. The structure typically includes status information about the disconnection request.

Example output JSON structure (simplified):

{
  "status": "success",
  "message": "Instance disconnected successfully"
}

If an error occurs, the output will contain an error field describing the issue.

No binary data is produced by this operation.

Dependencies

  • Requires valid credentials for the Evolution API, including:

    • Base URL of the API.
    • API key for authentication.
    • Instance name identifying the WhatsApp instance to manage.

  • Optionally requires credentials for an auxiliary API used for subscription validation.

  • The node makes HTTP requests to the Evolution API endpoints.

  • No additional environment variables are explicitly required beyond these credentials.

Troubleshooting

  • Invalid Credentials or Subscription Errors:
    If the node throws errors related to invalid API keys or subscription issues, verify that the provided API key credentials are correct and active.

  • Unknown Resource or Operation Errors:
    These indicate misconfiguration of the node parameters. Ensure the resource is set to "Instance" and the operation to "Disconnect Instance".

  • Network or API Endpoint Issues:
    Connectivity problems or incorrect base URLs can cause failures. Confirm network access and correct API endpoint configuration.

  • Error Handling:
    If the node is configured to continue on failure, errors will be returned in the output JSON under an error property for each failed item.

Links and References

Discussion