Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node operation allows sending media messages to a specified chat via the WaAPI service. It supports sending images, audio, or other media either by providing a direct URL or Base64 encoded content. Users can optionally add captions, specify filenames (required for Base64), and control how the media is sent (e.g., as a sticker, voice message, or document). This node is useful for automating multimedia communication in WhatsApp chats, such as sending promotional images, voice notes, or documents programmatically.
Practical examples:
- Sending a product image with a caption to a customer support group.
- Delivering an audio voice note as a voice message to a contact.
- Sharing a PDF document as a file attachment in a chat.
- Replying to a specific message with a media file.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (number) - identifies the instance of the API or service to use. |
| Chat Id | Chat ID (string) - target chat identifier in the format <countrycode><usernumber>@c.us for individuals or @g.us for groups. |
| Media Url | URL of the media file to send (string). |
| Media Base 64 | Base64 encoded media content (string). Alternative to Media Url; requires specifying Media Name. |
| Media Caption | Optional caption text for the media (string). |
| Media Name | Optional filename for the media (string). Required if using Base64 media content. |
| Reply To Message Id | Optional message ID to reply to, formatted as <fromMe>_<chatId>_<messageHash> (string). |
| Preview Link | Boolean flag indicating whether to show link previews for URLs included in the message. |
| As Sticker | Boolean flag to send the image as a sticker instead of a regular media message. |
| As Voice | Boolean flag to send audio media as a voice message. |
| As Document | Boolean flag to send the media as a document/file rather than inline media. |
Output
The node outputs JSON data representing the response from the WaAPI service after attempting to send the media message. This typically includes message metadata such as message IDs, status, timestamps, and any error information if the send failed.
If binary data is involved (e.g., media files), it is handled internally and not output directly by this node; the node focuses on sending media rather than receiving it.
Dependencies
- Requires an active connection to the WaAPI API service.
- Needs an API key credential configured in n8n for authenticating requests to WaAPI.
- The node uses HTTP requests to the base URL
https://waapi.app/api/v1. - Proper network access to the media URLs or ability to handle Base64 encoded media content.
Troubleshooting
Common issues:
- Invalid or missing Chat Id format will cause message sending to fail.
- Providing Base64 media without specifying a Media Name may result in errors.
- Network issues or invalid media URLs can prevent media from being sent.
- Incorrect API credentials or expired tokens will cause authentication failures.
Error messages and resolutions:
- "Invalid chat ID format" — Ensure the chat ID follows the required pattern (
<countrycode><number>@c.usor@g.us). - "Media name required for Base64 content" — Provide a valid filename when sending Base64 media.
- "Authentication failed" — Verify that the API key credential is correctly set up and has proper permissions.
- "Media not found or inaccessible" — Check that the media URL is publicly accessible or that the Base64 content is correctly encoded.
- "Invalid chat ID format" — Ensure the chat ID follows the required pattern (