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 with the Add Categories operation, the node sends a request to add new categories within the ScaleFluidly system.

Typical use cases include automating category management in sales or product systems, where categories need to be programmatically created or updated based on external data or workflows. For example, a user might automate adding new product categories when onboarding new product lines or syncing categories from another system.

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). This determines which ScaleFluidly instance the node interacts with.
Request JSON object representing the request body sent to the API for the Add Categories operation. This should contain the necessary data structure expected by the ScaleFluidly API to create categories.

Output

The node outputs an array of JSON objects corresponding to the responses received from the ScaleFluidly API for each input item processed. Each JSON object contains the API response data related to the Add Categories operation, typically including details about the newly added categories or any status messages returned by the API.

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

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 internal credential names are exposed; the node can use either a bearer token passed dynamically or configured n8n credentials for authentication.
  • No additional external services beyond the ScaleFluidly API are required.

Troubleshooting

  • Bearer token missing: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error "Bearer token not found". Ensure that the authorization token is correctly set in the input data or configured credentials.
  • Operation not found: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is not found. Verify that the operation parameter matches one of the supported operations.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before execution.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting corresponds to a valid ScaleFluidly API endpoint.

Links and References


This summary focuses on the Admin resource's Add Categories operation as requested, based on static analysis of the provided source code and property definitions.

Discussion