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 automation tasks. Specifically, for the Webhook resource and Delete Webhook operation, it allows users to remove a previously configured webhook URL from their WhatsApp instance managed by Evolution API.

Use cases include:

  • Disabling event notifications sent to your system when certain WhatsApp events occur.
  • Cleaning up or rotating webhook URLs as part of maintenance or security practices.
  • Managing webhook lifecycle programmatically within an n8n workflow.

Example scenario: You have set a webhook to receive message updates but want to stop receiving these notifications temporarily or permanently. Using this node operation, you can delete that webhook configuration without manual intervention.

Properties

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

Note: For the Delete Webhook operation, the "Additional Fields" are available but may not be used directly in the deletion process based on the code.

Output

The node outputs JSON data representing the response from the Evolution API after attempting to delete the webhook. The structure typically includes confirmation of deletion or error details if the operation failed.

Output example (conceptual):

{
  "success": true,
  "message": "Webhook deleted successfully"
}

If an error occurs, the output will contain an error field with the error message.

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.

  • Also requires credentials for an auxiliary API ("N8N Tools API") used for subscription and API key validation before making requests to the Evolution API.

  • The node sends HTTP requests to the Evolution API endpoints and expects JSON responses.

  • Proper configuration of these credentials in n8n is necessary for successful execution.

Troubleshooting

  • Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that both the Evolution API and the auxiliary API credentials are correctly set and active.

  • Unknown Resource or Operation Errors: These errors indicate misconfiguration of the resource or operation parameters. Ensure "Webhook" is selected as the resource and "Delete Webhook" as the operation.

  • HTTP Request Failures: Network issues or incorrect API endpoint configurations can cause failures. Check network connectivity and API base URL correctness.

  • Continue On Fail Behavior: If enabled, the node will return error details in the output JSON instead of stopping execution, useful for workflows handling multiple items.

Links and References

Discussion