SparkBot icon

SparkBot

Interact with SparkBot WhatsApp API

Actions148

Overview

This node integrates with the SparkBot WhatsApp API to manage WhatsApp numbers. Specifically, the Create Number operation under the WhatsApp Numbers resource allows users to create and register a new WhatsApp number within their SparkBot account.

Typical use cases include:

  • Automating the provisioning of WhatsApp numbers for customer support or marketing campaigns.
  • Managing multiple WhatsApp numbers programmatically as part of a larger communication platform.
  • Quickly setting up new WhatsApp channels with specific billing plans and configurations.

For example, a business could use this node to automatically add a new WhatsApp number with a "Business" subscription plan and assign it an alias for easy identification in their system.

Properties

Name Meaning
Alias Alias or name for the WhatsApp number (2-30 characters). Used to identify the number internally.
Billing Plan Subscription plan for the WhatsApp number. Options: Professional, Business, Enterprise, Gateway Professional, Gateway Business, Gateway Enterprise, Platform Professional, Platform Business, Platform Enterprise.
Additional Options Collection of optional settings:
- Description Optional description for the WhatsApp number (max 80 characters).
- Agent IDs List of agent IDs to provide shared chat access (only applicable for Platform plans).
- Payment Intent Payment intent ID string (starts with "pi_"), likely related to payment processing or invoicing.

Output

The node outputs JSON data representing the result of the create number operation. This typically includes details about the newly created WhatsApp number such as its ID, alias, billing plan, status, and any other 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 the SparkBot service being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API key credential.

Troubleshooting

  • Common issues:

    • Invalid alias length (must be between 2 and 30 characters).
    • Unsupported or misspelled billing plan option.
    • Providing agent IDs when using non-Platform plans will have no effect.
    • Incorrect or missing payment intent ID format.
    • Network or authentication errors if the API key is invalid or expired.
  • Error messages:

    • Errors from the API will be surfaced as error messages in the node output.
    • If the node is set to continue on fail, errors will appear in the JSON output under an error property.
    • To resolve, verify input parameters, ensure valid API credentials, and check network connectivity.

Links and References


If you need further details on other operations or resources, feel free to ask!

Discussion