Actions9
- Contact Actions
- Group Actions
- Message Actions
- Webhook Actions
Overview
This node integrates with the Avisa API to send text messages specifically to WhatsApp groups. It allows users to specify a target group by its ID and send a custom text message to that group. This is useful for automating group communications, such as sending announcements, alerts, or updates to multiple recipients simultaneously within a WhatsApp group.
Practical examples include:
- Sending event reminders to a community group.
- Broadcasting promotional messages to customer groups.
- Distributing internal team updates in a company WhatsApp group.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the WhatsApp group to which the message will be sent. Must be provided in full format or will be appended with "@g.us". |
| Message | The text content of the message to send to the specified group. |
Output
The node outputs an array of JSON objects representing the response from the Avisa API for each input item processed. Each object typically contains success status and any relevant data returned by the API after attempting to send the message.
If the message sending fails due to client errors (e.g., invalid group ID or authorization issues), the output includes an object with success: false and an error field describing the issue.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Avisa API via an API token credential.
- The node expects the base URL and API token to be configured in the credentials.
- Network access to the Avisa API endpoint is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Group ID: Ensure the Group ID is correct and formatted properly (ends with "@g.us" or will be appended automatically).
- Authorization failures: Verify that the API token credential is valid and has not expired.
- Network connectivity problems: Confirm that the server running n8n can reach the Avisa API endpoint.
Error Messages:
- Errors with HTTP status 400 or 401 indicate client-side issues such as bad requests or unauthorized access. The node captures these and returns an error message in the output JSON.
- Other unexpected errors will cause the node to throw exceptions unless "Continue On Fail" is enabled, in which case errors are included in the output array.
Links and References
- Avisa API Documentation (hypothetical link, replace with actual if available)