Salebot icon

Salebot

Sends data to Salebot

Overview

This node integrates with Salebot, a chatbot and customer engagement platform. It allows sending messages, callbacks, or saving variables associated with a client identified by a Client ID. Typical use cases include automating communication with clients via chatbots, triggering callback actions based on user interactions, or storing custom variables for personalized experiences.

Practical examples:

  • Sending a message to a client when they perform a specific action on your website.
  • Triggering a callback event in Salebot to handle complex workflows.
  • Saving client-specific variables such as email or preferences to tailor future interactions.

Properties

Name Meaning
Action The type of operation to perform. Options: "Send Message", "Send Callback", "Save Variables".
Client ID Identifier of the client to whom the action applies.
Message Text content of the message to send (only shown if Action is "Send Message").
Callback Text content of the callback to send (only shown if Action is "Send Callback").
Variables Collection of key-value pairs representing variables to save for the client (shown if Action is "Send Callback" or "Save Variables"). Each variable has:
- Variable Name: e.g., "client.email"
- Value: the value to assign

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Salebot API call made according to the selected action. The structure depends on the API response but generally reflects the success or failure of the requested operation.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Salebot API.
  • The node uses HTTP POST requests to communicate with Salebot endpoints.
  • No additional environment variables are required beyond the API credential configuration.

Troubleshooting

  • Unknown Action Error: If an unsupported action is specified, the node throws an error indicating the resource/action is not known. Ensure the "Action" property is set to one of the supported options.
  • Missing Required Fields: The node requires "Client ID" and depending on the action, either "Message", "Callback", or "Variables". Missing these will cause errors.
  • API Request Failures: Network issues or invalid API credentials can cause request failures. Verify the API key and network connectivity.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON.

Links and References

Discussion