WAHA API icon

WAHA API

Complete WhatsApp automation with WAHA API - Multi-engine support

Actions55

Session → Restart Session

AI-generated

Overview

The "Restart Session" operation in the WAHA API node allows users to restart an existing WhatsApp session by its name. This is useful when a session becomes unresponsive, disconnected, or requires a refresh without fully stopping and starting it manually. Restarting a session can help maintain continuous WhatsApp automation workflows, such as message sending, group management, or contact handling.

Practical examples:

  • Automatically restarting a session if a heartbeat check fails.
  • Refreshing a session after network interruptions to resume message processing.
  • Managing multiple WhatsApp sessions and programmatically restarting specific ones as needed.

Properties

Name Meaning
Session Name The name of the WhatsApp session to restart. This identifies which session to target.
Additional Fields A collection of optional fields (not specifically used for restart but available generally): Filename, Mimetype, Link Description, Link Title, Contact Name, Contact Number, Reaction, Limit, Download Media

Output

The output JSON contains the response from the WAHA API after attempting to restart the specified session. It typically includes status information about the session restart request, such as success confirmation or error details.

Example structure:

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

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

Dependencies

  • Requires a valid WAHA API base URL and API key credential configured in n8n.
  • Optionally uses an additional API key credential for N8N Tools API validation.
  • The node sends HTTP requests to the WAHA API endpoints to manage WhatsApp sessions.
  • Proper network access to the WAHA API service is necessary.

Troubleshooting

  • Invalid API Key or Subscription: If the N8N Tools API validation fails with 401 or 403 errors, verify that the API keys are correct and the subscription is active.
  • Unknown Session Name: If the session name does not exist or is misspelled, the API may return an error indicating the session was not found.
  • Network Issues: Connectivity problems to the WAHA API endpoint will cause request failures; ensure the endpoint is reachable.
  • Unhandled Operation Errors: If an unsupported operation is selected, the node throws an error specifying the unknown operation.
  • To resolve errors, check credentials, session names, and network connectivity.

Links and References

Discussion