WhatsApi icon

WhatsApi

Connect with WhatApp HTTP API

Overview

This node connects to a WhatsApp HTTP API to load the conversation history of a specific chat. It is useful for retrieving past messages from a particular WhatsApp chat session, enabling workflows that require access to chat logs, such as customer support ticketing, chat analytics, or message archiving.

For example, you can use this node to fetch all messages exchanged with a customer identified by their WhatsApp ID (jid) within a given phone session, then process or analyze those messages downstream in your workflow.

Properties

Name Meaning
Phone The session ID representing the WhatsApp phone number or account to use. Typically linked to your authenticated WhatsApp session.
To The chat JID (Jabber ID) identifying the target chat whose conversation you want to load. Usually formatted like a phone number followed by @s.whatsapp.net.

Output

The node outputs JSON data containing the loaded conversation messages from the specified chat. The exact structure depends on the WhatsApp HTTP API response but generally includes message details such as sender, timestamp, message content, and message type.

No binary data output is indicated.

Dependencies

  • Requires connection to a WhatsApp HTTP API service.
  • Needs an API URL and authentication credentials configured in n8n (e.g., an API key or token).
  • The node uses standard HTTP headers (Accept: application/json and Content-Type: application/json) for requests.

Troubleshooting

  • Invalid Session ID or Phone: If the session ID is incorrect or expired, the API may return authentication errors. Ensure your session ID corresponds to a valid active WhatsApp session.
  • Incorrect Chat JID: Providing an invalid or non-existent chat JID will result in no conversation data or errors. Verify the JID format and existence.
  • API Connectivity Issues: Network problems or incorrect API base URL configuration can cause request failures. Check your API endpoint and network connectivity.
  • Permission Denied or Unauthorized: Missing or invalid API credentials will prevent access. Confirm your API key/token is correctly set up in n8n credentials.

Links and References

Discussion