ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

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 Item operation, the node sends a request to add an item to a price book within the ScaleFluidly system.

Common scenarios where this node is beneficial include automating price book management in sales or inventory systems, updating pricing structures programmatically, or integrating price book updates into larger workflows that manage product catalogs or sales quotes.

For example, a user might use this node to automatically add new products to a price book when they are created in an external system, ensuring pricing data stays synchronized without manual intervention.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which backend instance the request will be sent to.
Request JSON object representing the request body to send with the API call. This contains the details of the price book item to add. It must be provided by the user and formatted according to the ScaleFluidly API specification for adding price book items.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object represents the API response for the respective request, typically including confirmation of the added price book item or error details if the operation failed.

If the API supports binary data in responses, it is not explicitly handled or output by this node based on the static analysis.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token (Bearer token) passed via the authorization header in the input data's JSON under headers.authorization. If no token is found in the first input item's headers, the node throws an error.
  • No internal credential names are exposed; users must provide valid authorization tokens as part of the input or configure credentials externally.
  • No additional n8n-specific environment variables are required beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found: The node expects an authorization token in the first input item's JSON headers under authorization. If missing, it throws an error. Ensure your input data includes a valid Bearer token in this location.
  • Operation not found: If the specified operation (intent) does not match any known mapping, the node throws an error indicating the operation is not found. Verify the operation name matches one of the supported ScaleFluidly API actions.
  • Invalid JSON in Request: The request_info property must contain valid JSON matching the API's expected schema. Malformed JSON or incorrect structure may cause API errors.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting corresponds to a valid and accessible ScaleFluidly API endpoint.

Links and References


Note: This summary is based solely on static code analysis and provided property definitions. Runtime behavior, dynamic imports, or external dependencies beyond those visible in the source code are not inferred.

Discussion