ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, pricing, configuration, admin tasks, and more. Specifically for the Quote resource and the Get DealData operation, it fetches detailed deal-related data from the ScaleFluidly system.

Typical use cases include:

  • Retrieving comprehensive deal information for sales or quoting processes.
  • Integrating deal data into workflows for analysis, reporting, or further automation.
  • Automating quote management by pulling deal details dynamically.

For example, a user might use this node to get deal data associated with a specific quote ID to update CRM records or trigger follow-up actions based on deal status.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). Determines which backend instance the request is sent to.
Request JSON object containing the request body parameters required by the "Get DealData" operation. This is a flexible JSON input where you specify the exact query or filters needed by the API endpoint.

Output

The node outputs an array of JSON objects representing the response from the ScaleFluidly API for the requested deal data. Each item in the output corresponds to one API response per input item processed.

  • The json field contains the parsed JSON response from the ScaleFluidly API.
  • No binary data output is produced by this node.

The structure of the JSON depends on the ScaleFluidly API's response schema for deal data, typically including fields such as deal identifiers, status, amounts, participants, timelines, and other metadata relevant to deals.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token (bearer token) passed via HTTP headers if available in input data.
  • The node supports using an n8n credential for ScaleFluidly API authentication but can also work with explicit bearer tokens provided in input headers.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no stored credential is configured, the node will throw an error. Ensure that either the input includes a valid authorization token or the node credentials are set up properly.
  • Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node will report an error. Verify that the operation name is correct and supported.
  • API request failures: Network issues, invalid environment URLs, or malformed request JSON can cause request errors. Check the environment setting and ensure the request JSON matches the expected API schema.
  • Empty or unexpected responses: Confirm that the request body contains all required parameters for the "Get DealData" operation and that the API endpoint is functioning correctly.

Links and References

Discussion