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 Associated Products operation, the node sends a request to add products associated with a price book in the ScaleFluidly system.

Typical use cases include automating product management within price books, updating pricing catalogs, or synchronizing product associations in sales or inventory systems. For example, a sales operations team could use this node to programmatically update which products are linked to specific price books based on changing business rules or promotions.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object representing the request body to be sent to the API for the selected operation. This contains all necessary data for adding price book associated products.

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 contains the API response data related to the requested operation.

If the API returns binary data (not indicated explicitly here), it would typically represent files or media associated with the operation, but this node primarily handles JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • No explicit external npm packages beyond n8n's standard workflow helpers are required.
  • The node expects the user to provide valid JSON request bodies matching the API schema for the operation.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token is stored, the node will throw an error. Ensure that the input JSON includes a valid authorization token in the headers or configure credentials properly.
  • Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation name matches one of the supported actions.
  • Invalid JSON in Request property: Since the request body must be valid JSON, malformed JSON will cause the API call to fail. Validate JSON syntax before running the node.
  • API connectivity issues: Check network access to the selected environment URL and ensure the API service is reachable.

Links and References


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

Discussion