Actions92
- Contact Actions
- Employee Actions
- Estimate Actions
- Invoice Actions
- Job Actions
- Line Item Actions
- Note Actions
- Setting Actions
- Supplier Actions
- Task Actions
- Technician Actions
- User Actions
- Website Actions
- WhatsApp Actions
Overview
This node interacts with the WibiClick API to perform various operations across multiple resources. Specifically, for the WhatsApp resource and the Get WhatsApp Messages by Contact operation, it retrieves WhatsApp messages associated with a specific contact's phone number from a given website.
This functionality is useful in scenarios where you want to automate workflows involving customer communication history on WhatsApp, such as:
- Fetching recent chat messages with a client for CRM or support ticketing systems.
- Analyzing message content for sentiment or keyword triggers.
- Archiving WhatsApp conversations linked to contacts in your system.
For example, you could use this node to pull the last 50 WhatsApp messages exchanged with a particular customer identified by their phone number on a specific website, then process or store these messages downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website from which to retrieve WhatsApp messages. |
| Phone Number | The phone number of the contact whose WhatsApp messages you want to fetch. |
| Limit | Maximum number of WhatsApp messages to return (default is 50). |
Output
The output JSON contains the WhatsApp messages retrieved for the specified contact. The structure corresponds directly to the response from the WibiClick API endpoint /whatsapp-messages-by-contact, including message details such as timestamps, sender info, message content, etc.
If the node is used with other WhatsApp operations, it may also output responses related to sending messages, checking numbers, saving messages, or sending documents.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WibiClick API via an API key credential.
- The node expects the API URL and API key to be configured in the credentials.
- The API must support the endpoint
/whatsapp-messages-by-contactthat accepts parameters: website ID, phone number, and limit.
Troubleshooting
- Missing or invalid Website ID: Ensure the Website ID provided is correct and corresponds to an existing website in your WibiClick account.
- Invalid or missing Phone Number: The phone number must be valid and formatted as expected by the API.
- API Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Empty Results: If no messages are returned, confirm that the contact has WhatsApp messages recorded under the specified website.
- Rate Limits or API Errors: Handle HTTP errors gracefully; the node throws errors if the API request fails unless "Continue On Fail" is enabled.
Links and References
- WibiClick API Documentation (Assumed, replace with actual link if available)
- WhatsApp Business API concepts for message retrieval and contact management.
This summary focuses solely on the static analysis of the execute() method logic for the WhatsApp resource and the Get WhatsApp Messages by Contact operation, based on the provided source code and property definitions.