ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations related to quotes, configuration, pricing, admin tasks, and MCP (Multi-Channel Processing) actions. It is designed to interact with different ScaleFluidly resources by sending HTTP requests to the appropriate endpoints based on the selected operation and environment.

Common scenarios where this node is beneficial include automating quote management, retrieving pricing information, configuring product settings, managing administrative data, and executing custom MCP intents. For example, a sales automation workflow could use this node to create or update quotes dynamically, fetch pricing details for products, or manage user permissions within ScaleFluidly.

Properties

Name Meaning
Environment The target environment URL for the API calls. Options:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object contains the data returned by the API endpoint invoked for the selected operation.

If the node interacts with binary data, it would be included in the output accordingly, but based on the static analysis, the primary output is JSON data representing API responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token passed via the authorization header in the input data or as a parameter for certain operations.
  • The node supports using an API key credential configured in n8n for authenticated requests if no explicit bearer token is provided.
  • No other external dependencies are required beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization token in its headers and no token has been previously stored, the node will throw an error indicating that the bearer token is missing. Ensure that the input data includes a valid authorization token or configure the node with proper credentials.
  • Operation not found: If the specified operation or intent does not match any known mapping, the node throws an error stating the operation was not found. Verify that the operation name is correct and supported by the node.
  • API request failures: Network issues, invalid tokens, or incorrect request bodies can cause API call failures. Check the API response messages for details and ensure all required parameters and authentication are correctly set.

Links and References


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

Discussion