ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, accounts, products, pricing, and administrative tasks. Specifically, for the Quote resource and the Create External Account operation, it sends a user-defined JSON request body to the ScaleFluidly API endpoint corresponding to creating an external account linked to a quote.

Common scenarios where this node is beneficial include automating the creation of external accounts within a sales or quoting workflow, integrating external account data into your CRM or ERP systems, or programmatically managing account-related data as part of a larger automation pipeline.

For example, you might use this node to:

  • Automatically create an external account when a new quote is generated.
  • Integrate external account creation into a multi-step sales process.
  • Synchronize external account data from other systems into ScaleFluidly via API calls.

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 request will be sent to.
Request The JSON-formatted request body containing the details required to create the external account. This must be provided by the user and should conform to the API's expected schema for creating an external account.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each output JSON object corresponds to the API response for the respective request.

  • The json output field contains the parsed JSON response from the ScaleFluidly API.
  • If the API returns binary data (not indicated in this operation), it would be handled accordingly, but for this operation, only JSON responses are expected.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • No explicit internal credential names are exposed; users must configure appropriate API authentication credentials in n8n if needed.
  • The node dynamically selects the API URL based on the chosen environment property.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior authorization header was stored, the node throws an error. Ensure that the input data includes valid authorization headers or that the node is configured with proper credentials.
  • Operation not found: If the specified operation or 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 and resource selection.
  • Invalid JSON in Request: Since the request body is user-provided JSON, malformed JSON will cause the API call to fail. Validate the JSON structure before running the node.
  • API Endpoint Unreachable: Selecting the wrong environment or having network issues may cause request failures. Confirm the environment URL and network connectivity.

Links and References


If you need further details about other operations or resources, please provide their names.

Discussion