ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations related to quotes, configuration, pricing, and administrative tasks within the ScaleFluidly platform. Specifically, for the Quote resource and the Update Status By Approver operation, it enables updating the status of a quote based on approval actions by designated approvers.

Common scenarios where this node is beneficial include automating quote management workflows, such as programmatically changing quote statuses after approvals, streamlining sales processes, or integrating quote status updates into larger automation pipelines.

For example, a sales team could use this node to automatically update a quote's status to "Approved" once an approver confirms it, triggering subsequent steps like order creation or notification dispatch.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request JSON object containing the request body specific to the operation. This includes all necessary data to update the quote status by approver.

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 result of the API call made for that particular input.

The json output field contains the parsed response from the API, which typically includes details about the updated quote status or confirmation of the action performed.

No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Needs an authorization token (Bearer token) provided in the input data headers or via configured credentials to authenticate API requests.
  • Optionally uses an API key credential configured in n8n for authentication if no explicit bearer token is found in the input.

Troubleshooting

  • Bearer token not found error: 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 the authorization token is correctly passed either in the input data headers or through the node’s credential configuration.
  • Operation not found error: If the specified operation (intent) does not match any known operation URL mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause API call failures. Check the environment setting, request JSON structure, and API authentication details.
  • Invalid JSON in Request property: The Request property must be valid JSON. Malformed JSON will cause errors during execution.

Links and References


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

Discussion