Quepasa (Whatsapp) icon

Quepasa (Whatsapp)

Non Official Whatsapp API

Actions10

Overview

The Quepasa (Whatsapp) node's "Message" resource with the "Where" operation allows users to query and retrieve WhatsApp messages from a Quepasa API instance. This operation is useful for searching or filtering messages based on specific criteria, such as retrieving recent messages, paginating through message history, or integrating WhatsApp data into automated workflows.

Common scenarios:

  • Fetching all or a limited number of WhatsApp messages for reporting or analysis.
  • Integrating WhatsApp message data into CRM or support systems.
  • Automating responses or actions based on incoming messages.

Practical example:
A business could use this node to automatically pull the latest 50 WhatsApp messages received by their bot and process them in n8n for sentiment analysis or customer support ticket creation.

Properties

Name Type Meaning
Authentication options Selects the authentication method: either custom parameters or predefined credentials.
BaseUrl string The base URL of the Quepasa API (required if using parameter-based authentication).
Token string The token for the WhatsApp bot (required if using parameter-based authentication).
Return All boolean Whether to return all matching messages or limit the results.
Limit number Maximum number of messages to return (used only if "Return All" is false).

Output

The output is an array of JSON objects, each representing a WhatsApp message retrieved from the Quepasa API. The exact structure depends on the API response, but typically includes fields such as:

[
  {
    "id": "string",
    "from": "string",
    "to": "string",
    "timestamp": "string",
    "body": "string",
    // ...other message-specific fields
  }
]
  • If the node encounters an error and "Continue On Fail" is enabled, the output may include an error field with the error message.

Dependencies

  • External Service: Requires access to a running Quepasa API instance.
  • Authentication: Either via direct BaseUrl/Token input or predefined n8n credentials (quepasaTokenAuthApi).
  • n8n Configuration: Credentials must be set up in n8n if using predefined authentication.

Troubleshooting

Common issues:

  • Invalid BaseUrl or Token: Ensure the BaseUrl and Token are correct and correspond to your Quepasa API instance.
  • Authentication errors: If credentials are incorrect or missing, you may see errors like Authentication failed or 401 Unauthorized.
  • API not reachable: Network issues or incorrect BaseUrl can result in connection errors.
  • Limit not respected: If "Return All" is true, the "Limit" property is ignored.

Error handling:

  • If "Continue On Fail" is enabled, errors for individual items will be included in the output with an error field.
  • Otherwise, the node will throw an error and stop execution.

Links and References

Discussion