SparkBot icon

SparkBot

Interact with SparkBot WhatsApp API

Actions148

Overview

This node integrates with the SparkBot WhatsApp API to manage WhatsApp sessions, specifically allowing users to start a WhatsApp session for a selected WhatsApp number (device). Starting a session is essential for enabling message sending and receiving through that WhatsApp number.

Common scenarios where this node is beneficial include:

  • Initializing or reinitializing a WhatsApp session before sending messages.
  • Managing multiple WhatsApp numbers by starting sessions on demand.
  • Automating session handling in workflows that require interaction with WhatsApp via SparkBot.

For example, a user can configure the node to start a session on a specific WhatsApp number and optionally wait until the session is fully available before proceeding with subsequent workflow steps.

Properties

Name Meaning
WhatsApp Number The ID of the WhatsApp number (device) on which to start the session. Options are loaded dynamically from available devices.
Wait For Session Boolean flag indicating whether to wait for the device session to become available before continuing. Waiting may delay the response up to 90 seconds.

Output

The node outputs JSON data representing the result of the session start operation. This typically includes information about the session status or confirmation that the session has started successfully.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the SparkBot WhatsApp API.
  • The node depends on the SparkBot service being accessible and properly configured.
  • The "WhatsApp Number" options are dynamically loaded, implying the node fetches available devices from the SparkBot API.

Troubleshooting

  • Session Start Delays: If "Wait For Session" is enabled, the node may take up to 90 seconds to respond. Users should be aware of this potential delay.
  • Invalid WhatsApp Number: Selecting a WhatsApp number that is not registered or unavailable may cause errors. Ensure the device ID is valid and active.
  • Authentication Errors: Missing or invalid API key credentials will prevent the node from communicating with the SparkBot API.
  • Network Issues: Connectivity problems with the SparkBot API endpoint can cause failures; verify network access and API availability.

Common error messages might include authentication failures, invalid device IDs, or timeouts waiting for session availability. Resolving these usually involves checking credentials, verifying device IDs, and ensuring network connectivity.

Links and References

Discussion