ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, and administration within the ScaleFluidly platform. Specifically for the Quote resource and the Insert AddressDetails operation, it allows users to insert or update address details associated with a quote in ScaleFluidly.

Common scenarios where this node is beneficial include automating quote management workflows, enriching quote data with detailed address information, and integrating ScaleFluidly quote data into broader business processes such as CRM or ERP systems.

For example, a sales automation workflow could use this node to add shipping or billing address details to a quote automatically when a new customer order is created, ensuring that all relevant address information is captured and synchronized with ScaleFluidly.

Properties

Name Meaning
Environment The target environment of the ScaleFluidly API. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object containing the request body for the Insert AddressDetails operation. This should include the address details data to be inserted or updated.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the Insert AddressDetails operation, typically including confirmation of the inserted address details or any error messages returned by the API.

If the API supports binary data output, it would be summarized here; however, based on the static analysis, this node primarily deals with JSON data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an API authentication token if provided in the input data headers or via configured credentials.
  • No internal credential names are exposed; users must provide a valid bearer token either through input headers or n8n credentials configured generically as "an API key credential."

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token and no token is stored in static workflow data, the node will throw an error. Ensure that the authorization token is correctly passed in the input or configured in credentials.
  • Operation not found: If the specified operation (intent) does not match any known ScaleFluidly API endpoints, the node will throw an error indicating the operation is not found. Verify the operation name matches supported actions.
  • API request failures: Network issues, invalid JSON in the request body, or incorrect environment URLs can cause request failures. Check the environment URL and the structure of the JSON request body.
  • Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause errors. Validate JSON syntax before execution.

Links and References


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

Discussion