Quepasa (Whatsapp) icon

Quepasa (Whatsapp)

Non Official Whatsapp API

Actions11

Overview

The Quepasa (Whatsapp) node's "Message: Revoke" operation allows you to revoke (i.e., delete or invalidate) a specific WhatsApp message by its unique ID using the Quepasa non-official WhatsApp API. This is useful in scenarios where you need to programmatically retract messages that were sent in error, contain sensitive information, or are no longer relevant.

Practical examples:

  • Automatically revoking messages containing incorrect information.
  • Removing messages after a certain period for privacy compliance.
  • Integrating with moderation workflows to retract inappropriate content.

Properties

Below are the input properties relevant to the "Message: Revoke" operation:

Display Name Type Meaning
Authentication options Selects how to authenticate: either by entering parameters manually or using predefined credentials.
BaseUrl string The base URL of the Quepasa API. Required if using manual parameter authentication. Example: https://api.quepasa.org:31000
Token string The token for your WhatsApp bot. Required if using manual parameter authentication. Used to authorize API requests.
Message ID string The unique identifier of the message you want to revoke.

Note:

  • "BaseUrl" and "Token" are only required when "Authentication" is set to "Parameters".
  • "Message ID" is always required for this operation.

Output

The output will be a JSON object representing the result of the revoke operation. While the exact structure depends on the API response, it typically includes fields such as:

{
  "success": true,
  "messageId": "string",
  "status": "revoked"
}
  • success: Indicates whether the revoke operation was successful.
  • messageId: The ID of the message that was targeted.
  • status: The new status of the message (e.g., "revoked").

If an error occurs, the output may include an error field with a descriptive message.

Dependencies

  • External Service: Requires access to the Quepasa WhatsApp API.
  • API Key/Token: You must provide a valid Token for authentication, either directly or via n8n credentials.
  • n8n Configuration: If using predefined credentials, ensure they are configured in n8n under "Quepasa Token Auth API".

Troubleshooting

Common Issues:

  • Invalid Token: If the provided token is incorrect or expired, authentication will fail.
  • Incorrect BaseUrl: Ensure the BaseUrl matches your Quepasa API endpoint.
  • Missing Message ID: The operation requires a valid Message ID; missing or incorrect IDs will cause errors.
  • Network Errors: Connectivity issues between n8n and the Quepasa API can prevent successful execution.

Error Messages:

  • "Authentication failed": Check your Token and BaseUrl.
  • "Message not found": Verify the Message ID exists and is correct.
  • "Insufficient permissions": Ensure your token has rights to revoke messages.

Links and References

Discussion