ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, and MCP. Specifically for the Admin resource and the Add Price Book operation, it enables adding a new price book by sending a JSON request body to the appropriate ScaleFluidly API endpoint.

Common scenarios where this node is beneficial include automating price book management within sales or inventory systems, integrating pricing updates into workflows, or synchronizing price books between different environments (Dev, QA, Local).

For example, a user can automate the creation of a new price book in the Dev environment by providing the necessary details in JSON format, which the node sends to the ScaleFluidly API, streamlining price management without manual API calls.

Properties

Name Meaning
Environment The target environment for the API call. Options: "Dev" (https://documentation-dev.scalefluidly.com), "QA" (https://documentation.scalefluidly.com), "Local" (http://localhost:8400). Determines the base URL for the API requests.
Request The JSON-formatted request body containing the data required to add a price book. This must be provided according to the API's expected schema for adding a price book.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the Add Price Book operation, typically including confirmation details or the created price book data.

If the API supports binary data in responses, the node would handle it accordingly, but based on the static analysis, the output focuses on JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoints corresponding to the selected environment.
  • Optionally uses an API authentication token passed via an authorization header. If not explicitly provided in the input data headers, the node attempts to use stored credentials configured in n8n.
  • No other external dependencies are indicated.

Troubleshooting

  • Bearer token not found error: This occurs if the first input item does not contain an authorization token in its headers and no stored credential is available. To resolve, ensure that either the input includes a valid bearer token in the authorization header or configure the node with the required API authentication credentials.
  • Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node throws an error. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: Since the request body must be valid JSON matching the API schema, malformed JSON or missing required fields will cause API errors. Validate the JSON structure before execution.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL may lead to connection failures. Confirm the environment setting matches the intended API server.

Links and References

Note: Replace URLs with actual documentation links if available.

Discussion