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 instances and perform various operations related to WhatsApp automation. Specifically, the Delete Instance operation under the Instance resource allows users to delete a WhatsApp instance managed by the Evolution API.

Use cases for this node include automating WhatsApp workflows such as creating, connecting, disconnecting, and deleting WhatsApp instances programmatically. The Delete Instance operation is useful when you want to remove an existing WhatsApp instance from your system, for example, when decommissioning or cleaning up unused instances.

Practical example:

  • Automatically delete a WhatsApp instance after a certain period of inactivity.
  • Remove test instances created during development or QA processes.

Properties

Name Meaning
Additional Fields Optional extra parameters:
- Delay: Delay in milliseconds before sending the request.
- 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 messages.

Note: For the Delete Instance operation specifically, the node does not require additional input properties beyond those inherited from the resource and operation selection. The "Additional Fields" collection is available but may not be applicable for this operation.

Output

The node outputs JSON data representing the response from the Evolution API after attempting to delete the instance. The structure typically includes status information about the deletion request, such as success confirmation or error details.

Example output JSON structure (simplified):

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

If the operation fails, the output will contain an error message describing the issue.

The node does not output binary data.

Dependencies

  • Requires an API key credential for the Evolution API to authenticate requests.
  • Optionally uses another API key credential for an auxiliary validation service ("N8N Tools API") to validate subscription and API key before making the main request.
  • The node expects configuration of these credentials within n8n.
  • The node sends HTTP requests to the configured base URL of the Evolution API.

Troubleshooting

  • Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that the provided API keys are correct and active.
  • Unknown resource or operation errors: These occur if the resource or operation parameters are set incorrectly. Ensure the resource is set to "Instance" and operation to "Delete Instance".
  • Network or connectivity issues: Check that the Evolution API base URL is reachable from the n8n environment.
  • API rate limits or permission errors: Confirm that the API key has sufficient permissions to delete instances and that you have not exceeded any usage limits.

Links and References

Discussion