ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, specifically supporting various administrative, pricing, quote, configuration, and MCP-related operations. For the Admin resource with the Get Pricing Customer Lookup operation, it allows users to send a custom JSON request body to the ScaleFluidly API endpoint that performs customer lookup related to pricing.

Typical use cases include:

  • Retrieving detailed pricing customer information for administrative purposes.
  • Integrating pricing customer data into workflows for further processing or decision-making.
  • Automating customer lookup tasks within sales or pricing pipelines.

Example: A user can input specific customer identifiers or filters in the JSON request body to fetch relevant pricing customer details from the ScaleFluidly system.

Properties

Name Meaning
Environment The target environment for the API call. Options are:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object representing the request body sent to the API. This contains parameters required by the "Get Pricing Customer Lookup" operation to specify which customer data to retrieve.

Output

The node outputs an array of JSON objects corresponding to the API response(s) from the ScaleFluidly service. Each item in the output array represents the parsed JSON response from the executed API call.

  • The json field contains the full response data returned by the ScaleFluidly API for the pricing customer lookup.
  • No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use configured credentials named generically as an API key credential.
  • The node requires proper network access to the selected environment URL.
  • No additional external libraries beyond n8n's standard HTTP request helpers are needed.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no API credential is configured, the node will throw an error. Ensure that either the input includes a valid authorization header or the node is configured with appropriate API credentials.
  • Operation not found error: If the specified operation or intent name does not match any known API endpoint mapping, the node will report an error. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause the API call to fail. Validate the JSON syntax before execution.
  • Network or environment issues: Ensure the selected environment URL is reachable and correct.

Links and References


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

Discussion