ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations across multiple resources such as quotes, configuration, pricing, admin, and MCP. Specifically, for the Configure resource and the Add Products To Quote operation, it allows users to add product details to an existing quote within the ScaleFluidly system.

Common scenarios where this node is beneficial include automating quote management workflows by programmatically updating quotes with new products, integrating product catalog updates into sales processes, or synchronizing product selections from external systems into ScaleFluidly quotes.

For example, a sales automation workflow could use this node to add selected products to a quote after a customer finalizes their product choices on a website, ensuring the quote reflects the latest product configuration without manual intervention.

Properties

Name Meaning
Environment The target environment of the ScaleFluidly API. Options are:
- Dev: Development environment
- QA: Quality Assurance environment
- Local: Localhost instance (for testing)
Request JSON object representing the request body sent to the ScaleFluidly API for the operation. This contains all necessary data to add products to the quote, such as product IDs, quantities, pricing details, etc.

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 represents the result of adding products to a quote, typically including confirmation details, updated quote information, or error messages if the operation failed.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token (bearer token) passed via the input item's headers.authorization field or through configured credentials.
  • No other external dependencies are required.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no credential is configured, the node will throw an error. Ensure that either the input includes a valid authorization token or the node is configured with appropriate API credentials.
  • Operation not found: If the specified operation (intent) does not match any known API endpoint mapping, the node will throw an error indicating the operation is not found. Verify the operation name is correct and supported.
  • Invalid request body: Since the request body is user-provided JSON, malformed or incomplete JSON may cause API errors. Validate the JSON structure before running the node.
  • API connectivity issues: Network problems or incorrect environment URLs can cause request failures. Confirm the environment URL is reachable and correct.

Links and References


If you need further details about other operations or resources, please provide additional context.

Discussion