N8N Tools - Yup.chat icon

N8N Tools - Yup.chat

Send messages and manage communications through Yup.chat

Actions17

Overview

This node integrates with the Yup.chat API to manage WhatsApp messages within n8n workflows. Specifically, the Get Messages operation under the WhatsApp Messages resource allows users to retrieve messages from a specified WhatsApp conversation room.

Typical use cases include:

  • Fetching recent WhatsApp chat messages for processing or analysis.
  • Automating message retrieval for customer support or CRM systems.
  • Archiving or monitoring WhatsApp conversations programmatically.

For example, you can configure this node to pull the last 100 messages from a particular WhatsApp room and then use subsequent nodes to analyze sentiment or extract key information.

Properties

Name Meaning
Return All Whether to return all available messages or limit the number of results returned.
Limit Maximum number of messages to return if "Return All" is set to false (1 to 500).

These properties control how many messages are fetched from the WhatsApp conversation room.

Output

The node outputs an array of JSON objects representing individual WhatsApp messages retrieved from the specified room. Each item in the output corresponds to one message object as returned by the Yup.chat API.

The exact structure of each message object depends on the API response but typically includes fields such as message content, sender info, timestamps, and message metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Yup.chat API key credential configured in n8n.
  • The node makes HTTP requests to the Yup.chat API endpoint (default: https://api.yup.chat).
  • Proper permissions and valid API credentials are necessary to access WhatsApp message data.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Incorrect Room ID will result in not found or empty responses.
    • Exceeding rate limits imposed by Yup.chat API may cause request failures.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
    • "Room not found" or similar errors suggest the provided Room ID does not exist or is inaccessible.
    • Network or timeout errors may require checking connectivity or retrying later.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to prevent workflow interruption.

Links and References

Discussion