Actions50
- Message Actions
- Contact Actions
- Account Actions
- Call Actions
- Chat Actions
- Group Actions
- Instance Actions
- Media Actions
- Session Actions
- User Actions
Overview
This node enables sending a sticker message via WhatsApp using the WSAPI WhatsApp API. It is part of a broader integration that supports various WhatsApp messaging operations. The "Send Sticker" operation specifically allows users to send a sticker to a WhatsApp contact or group by providing a publicly accessible URL to the sticker media.
Common scenarios where this node is beneficial:
- Automating customer engagement by sending branded or custom stickers in response to user actions.
- Enhancing chatbots with rich media content like stickers for better user interaction.
- Broadcasting promotional or informational stickers to groups or individual contacts.
Practical example:
- A marketing automation workflow sends a welcome sticker to new customers who join a WhatsApp group.
- A support bot replies with a confirmation sticker after resolving a user's query.
Properties
| Name | Meaning |
|---|---|
| To | The WhatsApp contact ID or group ID to which the sticker will be sent. For contacts, use the phone number followed by @s.whatsapp.net (e.g., 1234567890@s.whatsapp.net). For groups, use the group ID followed by @g.us. |
| Media URL | The direct HTTP or HTTPS URL of the sticker media file to send. Must be publicly accessible. Supported formats depend on WhatsApp's sticker requirements (usually WebP format). |
| Advanced Options | Additional optional settings: - Mentions: Comma-separated list of phone numbers (without @) to mention in the message.- Reply To Message ID: ID of a message to reply to. - Is Forwarded: Boolean indicating if the message is forwarded. - View Once: (Not applicable for stickers) Whether the message should disappear after being viewed (only for media like images/videos). |
Output
The node outputs an array of JSON objects representing the result of the send sticker operation. Each output item typically contains metadata about the sent message such as message ID, status, timestamps, and recipient information.
If the operation involves binary data (not typical for sending stickers via URL), it would be included accordingly, but for this operation, the output is primarily JSON metadata confirming the message was sent.
Dependencies
- Requires an active connection to the WSAPI WhatsApp API service.
- Needs an API key credential configured in n8n to authenticate requests.
- The media URL must be publicly accessible over HTTP or HTTPS; no authentication on the media URL is supported.
- Proper formatting of WhatsApp IDs (
toproperty) is essential (phone number + domain suffix).
Troubleshooting
- Invalid Contact or Group ID: Ensure the
Tofield uses the correct format (number@s.whatsapp.netfor contacts,groupid@g.usfor groups). Incorrect formatting will cause message sending failures. - Media URL Not Accessible: The provided
Media URLmust be publicly reachable. If the URL is behind authentication or inaccessible, the sticker will not send. - Unsupported Media Format: Stickers usually require specific formats (e.g., WebP). Using unsupported formats may cause errors.
- API Authentication Errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Message Reply or Mentions Failures: When using advanced options like replying to a message or mentioning users, ensure the referenced message ID or phone numbers are valid and exist in the chat context.