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 with the Get Based On Price Books operation, it enables retrieval of administrative data related to price books from the ScaleFluidly system.

Common scenarios where this node is beneficial include:

  • Automating administrative tasks related to pricing structures.
  • Fetching price book details to synchronize or analyze pricing data.
  • Integrating ScaleFluidly's admin capabilities into broader workflows for sales or product management.

For example, a user might use this node to fetch all price books associated with certain categories or products to update pricing strategies dynamically in their CRM or ERP systems.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.
  • Environment selects which ScaleFluidly API endpoint to interact with, useful for development, testing, or production usage.

Output

The node outputs an array of JSON objects representing the response(s) from the ScaleFluidly API for the requested operation. Each item corresponds to the data returned by the API call, typically including details about price books or related administrative information.

If the API returns binary data (not evident in this operation), it would be included accordingly, but for this operation, the output is purely JSON.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • Optionally uses an API authentication token passed via HTTP headers (Bearer token).
  • No explicit internal credential type names are exposed; users must provide appropriate API authentication configured in n8n or via input data headers.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a Bearer token, the node will throw an error. Ensure that the input data includes valid authorization headers or that credentials are properly configured.
  • Operation not found error: If the specified operation does not map to a known intent URL, the node will report this. Verify that the operation name matches one of the supported operations for the Admin resource.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check connectivity and authentication details.
  • Empty or malformed request body: Some operations require a JSON request body. Make sure the "Request" property contains valid JSON if needed.

Links and References


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

Discussion