WasenderAPI icon

WasenderAPI

Manage WasenderAPI sessions, messages, contacts, and groups

Actions53

Message → Send Sticker

AI-generated

Overview

This node operation sends a sticker message via the WasenderAPI. It is useful for automating the sending of sticker content to individual recipients, groups, or channels on WhatsApp. For example, it can be used in marketing campaigns, customer engagement, or interactive chatbots to send stickers as part of the conversation.

Use Case Examples

  1. Sending a sticker to a customer to enhance engagement in a support chat.
  2. Automating sticker sending in a group chat for event announcements or fun interactions.

Properties

Name Meaning
Session Selects the WhatsApp session to use for sending the sticker. It can be chosen from a list or by ID, or automatically selected from the incoming item.
Recipient The phone number, group JID, or channel JID to which the sticker will be sent. This is required.
Sticker URL The URL of the sticker image (in .webp format) to be sent. This is required.
Message Options Additional options for the message, such as replying to a specific message ID.
Mentions Used for group messages to mention specific members by their participant JIDs.
Options Request options including retry behavior for failed requests and maximum retry attempts.

Output

JSON

  • to - The recipient's identifier (phone number, group JID, or channel JID).
  • stickerUrl - The URL of the sticker sent.
  • replyTo - The ID of the message this sticker is replying to, if any.
  • mentions - List of participant JIDs mentioned in the message, if any.
  • messageId - The unique identifier of the sent sticker message.
  • status - The status of the message sending operation.

Dependencies

  • WasenderAPI service with an API key credential for authentication.

Troubleshooting

  • Ensure the session ID is correctly selected or provided; otherwise, the node will throw an error indicating a session is required.
  • The sticker URL must be a valid .webp image URL; invalid URLs or unsupported formats will cause the request to fail.
  • If replying to a message, the Reply To Message ID must be a positive integer; otherwise, an error will be thrown.
  • Network or API errors may occur; the node supports retry options to handle transient failures such as HTTP 408, 429, 500, 502, or 503 errors.

Discussion