Actions37
- Message Actions
- Media Actions
- Contact Actions
- Group Actions
- Instance Actions
- Webhook Actions
Overview
This node integrates with the Uazapi WhatsApp API, enabling users to send and manage WhatsApp messages programmatically within n8n workflows. Specifically, the "Get Messages" operation under the "Message" resource retrieves the message history for a specified WhatsApp number.
Common scenarios where this node is beneficial include:
- Fetching recent chat history for customer support or CRM systems.
- Archiving or analyzing WhatsApp conversations automatically.
- Triggering workflows based on received messages.
For example, a user can configure this node to get the last 50 messages from a customer's WhatsApp number to analyze conversation context before sending an automated reply.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional parameters to customize the request: |
| - Reply to Message ID: ID of a message to reply to | |
| - Delay (seconds): Delay before sending a message | |
| - Disable Link Preview: Whether to disable link previews in messages (true/false) | |
| - Mention Users: Comma-separated phone numbers to mention in the message |
Note: For the "Get Messages" operation, the relevant additional field is limit (not explicitly listed in your provided properties but used internally), which controls how many messages to retrieve (default 50).
Output
The node outputs an array of JSON objects representing the retrieved messages. Each item corresponds to one input item processed and contains the full response from the Uazapi API for the message history request.
The exact structure of each message object depends on the Uazapi API response but typically includes details such as message IDs, timestamps, sender and receiver information, message content, and status.
No binary data output is produced by this operation.
Dependencies
- Requires an active Uazapi WhatsApp API account.
- Needs credentials including an API key, API token, API URL, and instance ID configured in n8n.
- The node sends requests through a proxy endpoint (
https://n8ntools.io/api/v1/proxy/uazapi) using the provided API key credential. - Proper network access to the Uazapi service is necessary.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication failures.
- Incorrect instance ID or phone number may result in empty or error responses.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Errors returned from the Uazapi API are passed through; typical messages might indicate invalid parameters or authorization errors.
- If the node throws an error about unknown resources or operations, verify that the Resource is set to "Message" and Operation to "Get Messages".
- To handle intermittent failures gracefully, enable "Continue On Fail" in the node settings.
Links and References
- Uazapi Official Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general usage of custom nodes and credentials)
If you need details on other operations or resources, feel free to ask!