ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various operations across multiple resources such as Admin, Quote, Configure, Pricing, MCP, and Product. Specifically for the Admin resource and the Get Deal Guidances operation, the node fetches deal guidance data from the ScaleFluidly platform.

Typical use cases include:

  • Retrieving deal guidance information to assist sales or account teams in making informed decisions.
  • Automating workflows that require up-to-date deal guidance data from ScaleFluidly.
  • Integrating deal guidance insights into broader business processes or dashboards.

For example, a user might configure this node to pull deal guidance details for a specific environment (Dev, QA, or Local) to analyze or display within their CRM or reporting tools.

Properties

Name Meaning
Environment The target ScaleFluidly environment to connect to. Options: Dev, QA, Local (with URLs).

Note: The node also requires selecting the Resource (Admin) and Operation (Get Deal Guidances), but these are fixed by your input context.

Output

The node outputs an array of JSON objects under the json output field. Each object corresponds to the response received from the ScaleFluidly API for the requested deal guidances.

  • The structure of each JSON object depends on the API's response schema for deal guidances.
  • The node does not output binary data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint corresponding to the selected environment.
  • Optionally uses an authorization bearer token extracted from the first input item's JSON headers (authorization header).
  • If no bearer token is found in the input, the node attempts to use an API authentication credential configured in n8n (if available).
  • No other external dependencies are required.

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.
    Resolution: Ensure the input data includes a valid bearer token in the headers or configure the appropriate API authentication credential in n8n.

  • Operation not found error:
    If the specified operation (intent) does not map to a known URL endpoint, the node throws an error indicating the operation was not found.
    Resolution: Verify that the operation name matches one of the supported operations for the Admin resource.

  • API request failures:
    Network issues, invalid tokens, or incorrect environment URLs can cause request failures.
    Resolution: Confirm the environment URL is correct and accessible, and that the authorization token is valid.

Links and References

Note: Replace links with actual documentation URLs relevant to your environment if different.

Discussion