WAHA APIInstall

Overview

The "Stop Session" operation of the WAHA API node allows users to stop a specific WhatsApp session by its name. This is useful in scenarios where you want to programmatically terminate an active WhatsApp session, for example, to free up resources, reset the session state, or manage multiple sessions dynamically.

Practical examples include:

• Automatically stopping a session after a certain workflow completes.
• Managing session lifecycle in multi-session environments.
• Stopping sessions before restarting or logging out to ensure clean transitions.

Properties

The "Additional Fields" collection includes options like Filename, Mimetype, Link Description, Link Title, Contact Name, Contact Number, Reaction emoji, Limit for results, and Download Media flag. These are not relevant for the Stop Session operation itself but are part of the node's general input properties.

Output

The output JSON contains the response from the WAHA API after attempting to stop the specified session. It typically includes status information about the session termination request.

Example structure:

{
  "status": "success",
  "message": "Session stopped successfully",
  "session": "sessionName"
}

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

Dependencies

• Requires an API key credential for the WAHA API service.
• 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 makes HTTP requests to the configured WAHA API base URL.
• Requires proper configuration of credentials in n8n for both WAHA API and optionally N8N Tools API.

Troubleshooting

• Invalid subscription or API key: If the auxiliary validation fails with 401 or 403 errors, check that the API keys are correct and have valid subscriptions.
• Unknown session operation: If the operation parameter is incorrect or unsupported, the node throws an error indicating the unknown operation.
• Network or API errors: Standard HTTP errors from the WAHA API will be returned in the output; ensure the base URL and API key are correctly set.
• Session not found: If the session name does not exist or is misspelled, the API may return an error indicating the session could not be stopped.

Links and References

• WAHA API Documentation (replace with actual URL if available)
• n8n Documentation on Custom Nodes
• WhatsApp Automation Concepts

This summary focuses on the "Stop Session" operation within the "Session" resource of the WAHA API node as requested.