Actions33
Overview
This node interacts with the Quepasa (Whatsapp) API to perform operations related to messages. Specifically, the 'Where' operation under the 'Message' resource allows users to query and retrieve messages based on certain criteria. It supports fetching either all matching messages or a limited number of results, making it useful for scenarios where users need to filter and analyze Whatsapp messages programmatically.
Use Case Examples
- A user wants to retrieve all messages that meet specific conditions from their Whatsapp bot for analysis.
- A user needs to fetch a limited number of recent messages matching certain criteria to display in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the API requests, either by providing parameters directly or using predefined credentials. |
| BaseUrl | The base URL of the Quepasa API endpoint, required when using parameter-based authentication. |
| Token | The token of the Whatsapp bot used for authentication, required when using parameter-based authentication. |
| Return All | Determines whether to return all matching messages or limit the number of results. |
| Limit | Specifies the maximum number of messages to return when 'Return All' is false. |
Output
JSON
id- Unique identifier of the message.from- Sender of the message.to- Recipient of the message.body- Content of the message.timestamp- Time when the message was sent or received.
Dependencies
- Quepasa API, requiring either parameter-based authentication (BaseUrl and Token) or predefined credentials with an API token.
Troubleshooting
- Common issues include authentication failures due to incorrect BaseUrl or Token, which result in error messages indicating authentication errors. Users should verify their credentials and ensure the API endpoint is reachable.
- If the node returns fewer messages than expected, check the 'Return All' and 'Limit' settings to ensure they are configured correctly.
- Network or API downtime can cause request failures; retrying or checking API status is recommended.