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 Pricing, Quote, Configure, MCP, and Admin. Specifically for the Pricing resource and the Product Ramps operation, it enables retrieval or manipulation of product ramp data related to pricing strategies.

Common scenarios where this node is beneficial include:

  • Automating price ramp retrievals for products in a pricing catalog.
  • Integrating pricing adjustments dynamically into workflows.
  • Fetching detailed ramp structures for products to support sales or finance processes.

For example, a user might use this node to fetch all product ramps associated with a specific price book or category to analyze tiered pricing or volume discounts programmatically.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (with respective URLs).
Request JSON object representing the request body payload sent to the API endpoint for the selected operation. This contains parameters specific to the Product Ramps operation.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response from the ScaleFluidly API for the requested operation. For the Product Ramps operation, the output typically includes details about product ramp configurations such as ramp tiers, pricing steps, quantities, and related metadata.

If the API returns binary data (not indicated explicitly here), it would be included accordingly, but based on the static analysis, the output is JSON structured data representing pricing ramp information.

Dependencies

  • Requires access to the ScaleFluidly API endpoints, which differ based on the selected environment (Dev, QA, Local).
  • Optionally uses an API authentication token passed via an authorization header. If not provided explicitly in input data headers, the node expects a stored credential or token configured in n8n.
  • No other external dependencies are required beyond standard HTTP request capabilities.

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 credentials are available. To resolve, ensure that the API token is provided either in the input data headers or configured as a credential in n8n.
  • Operation not found error: If the specified operation (intent) does not match any known mapping, the node throws an error. Verify that the operation name is correct and supported by the node.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause errors. Confirm the environment URL is reachable and the request JSON matches the expected schema for the Product Ramps operation.

Links and References


Note: This summary is based solely on static code analysis of the provided source and property definitions without runtime execution.

Discussion