SparkBot icon

SparkBot

Interact with SparkBot WhatsApp API

Actions148

Overview

This node allows scheduling WhatsApp messages to be sent via the SparkBot WhatsApp API. It supports sending text messages at a specified future date and time, enabling automation of message delivery for reminders, notifications, marketing campaigns, or customer engagement.

Typical use cases include:

  • Scheduling appointment reminders to customers.
  • Sending promotional messages at optimal times.
  • Automating follow-up messages in customer support workflows.

By specifying the delivery date/time, users can plan communications ahead without manual intervention.

Properties

Name Meaning
WhatsApp number The SparkBot Number ID used as the sender for the message delivery.
Target Type of target chat: Phone (individual), Group, or Channel.
Phone Number Target phone number in international E.164 format (e.g., +1234567890). Required if Target is Phone.
Group ID ID of the target group chat (e.g., 12345678902401234@g.us). Required if Target is Group.
Channel ID ID of the target channel (e.g., 12345678902402200@newsletter). Required if Target is Channel.
Message Text content of the message to be sent (up to 6000 characters).
Delivery date Date and time when the message should be delivered (scheduled send time).
Options Collection of optional settings including:
- Priority: Normal, High, Low
- Label: Custom label to categorize the message
- Reference ID: Custom reference identifier
- Team Agent: Send on behalf of an agent
- Live mode: Real-time sending without queue (riskier)
- Delivery Queue Mode: Controls queuing behavior (default, always queue, never queue, opportunistic)
- Maximum Retries: Number of retry attempts for delivery
- Chat Actions: Post-delivery actions like assigning chat, resolving, adding/removing labels or metadata
Message Expiration Defines message TTL (time-to-live) with options to expire after seconds, duration (e.g., "1h"), or specific date/time.
Mark Chat as Read Boolean to notify WhatsApp that previous unread messages will be marked as read after delivery (blue double-check).
Typing simulation Seconds to simulate typing or recording status before sending (0 disables). Useful for more natural interaction.
Quote Message Message ID to quote when sending this message (must be in same conversation).
Strict Message Order Ensures messages are sent in strict order to the target chat. Not compatible with live mode or never queue delivery. Useful for chatbots or sequences.

Output

The node outputs JSON data representing the result of the scheduled message operation. This typically includes confirmation details such as message IDs, status, and any metadata returned by the SparkBot API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the SparkBot WhatsApp API.
  • The node depends on SparkBot's backend services for message scheduling and delivery.
  • Some properties load dynamic options from the API, such as available devices (WhatsApp numbers), groups, channels, labels, team agents, and departments.
  • Proper configuration of these resources in SparkBot is necessary for successful operation.

Troubleshooting

  • Invalid phone number format: The phone number must be in E.164 format (e.g., +1234567890). Errors occur if the regex validation fails.
  • Missing required fields: Ensure that the correct target type is selected and corresponding fields (phone, groupId, or channel) are provided.
  • Delivery failures: If messages fail to deliver, check the maximum retries setting and delivery queue mode. Using real-time mode ("never queue") for high volume may cause bans or throttling.
  • Agent or department assignment errors: When using chat actions to assign chats, ensure valid 24-character hexadecimal IDs are provided.
  • Typing simulation limits: Values must be between 0 and 30 seconds; invalid values may cause errors.
  • Quote message ID validation: Quoted message IDs must be 18-32 hex characters and belong to the same conversation.
  • Strict order conflicts: Enabling strict message order is incompatible with live mode or never queue options; avoid combining these settings.

Links and References

Discussion