Quepasa (Whatsapp) icon

Quepasa (Whatsapp)

Non Official Whatsapp API

Actions11

Overview

This n8n node, Quepasa (Whatsapp), provides integration with a non-official WhatsApp API called Quepasa. It allows users to interact with WhatsApp functionalities such as sending messages, managing webhooks, retrieving information, and performing control operations through automated workflows in n8n.

Common scenarios:

  • Sending WhatsApp messages automatically from business systems.
  • Receiving and processing incoming WhatsApp messages via webhooks.
  • Retrieving bot or account information for monitoring or reporting.
  • Managing WhatsApp bot controls programmatically.

Practical examples:

  • Automatically notify customers on WhatsApp when their order status changes.
  • Set up a webhook to trigger n8n workflows when new WhatsApp messages are received.
  • Fetch and log WhatsApp bot status or usage statistics.

Properties

Below are the supported input properties relevant to the "Default" Resource and Operation:

Display Name Type Meaning
Authentication options Selects the authentication method:
- Parameters: Use custom BaseUrl and Token.
- Predefined Quepasa Credentials: Use credentials stored in n8n.
BaseUrl string The base URL of the Quepasa API. Required if using "Parameters" authentication. Example: https://api.quepasa.org:31000
Token string The token for the WhatsApp bot. Required if using "Parameters" authentication. This overrides any credentials.

Output

The output structure depends on the selected resource and operation. For the default case (when no specific resource/operation is provided), the node returns an array of JSON objects, each representing the result of the performed action.

  • If the operation involves fetching information, sending messages, or managing webhooks/control, the output will be a JSON object (or array of objects) containing the response data from the Quepasa API.
  • In case of errors and if "Continue On Fail" is enabled, the output may include an error field with the error message.

Example output:

[
  {
    "status": "success",
    "data": { /* ...API-specific fields... */ }
  }
]

or, in case of error:

[
  {
    "error": "Invalid token"
  }
]

If the operation is a download or involves binary data, the node prepares the output accordingly, but details depend on the specific operation chosen.

Dependencies

  • External Service: Requires access to the Quepasa (WhatsApp) API endpoint.
  • Authentication: Either provide a BaseUrl and Token directly, or use predefined credentials configured in n8n.
  • n8n Configuration: If using predefined credentials, ensure that the credential type quepasaTokenAuthApi is set up in n8n.

Troubleshooting

Common issues:

  • Invalid BaseUrl or Token: If the BaseUrl or Token is incorrect, authentication will fail.
  • Missing required fields: Not providing required fields (BaseUrl, Token) when using "Parameters" authentication will cause errors.
  • API connectivity issues: Network problems or incorrect API endpoints can lead to request failures.

Error messages:

  • "Authentication successful": Indicates successful connection during credential testing.
  • "Invalid token" or similar: Check your Token value and ensure it matches your Quepasa bot's credentials.
  • "Cannot read property 'body' of undefined": Likely due to unexpected API response; check API availability and parameters.

How to resolve:

  • Double-check all input values, especially BaseUrl and Token.
  • Ensure the Quepasa API is reachable from your n8n instance.
  • If using predefined credentials, verify they are correctly configured in n8n.

Links and References

Discussion