ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, admin tasks, and more. Specifically for the Quote resource and the Get HighValueDealsData operation, it sends a custom JSON request body to the ScaleFluidly API endpoint corresponding to retrieving high-value deals data.

Typical use cases include:

  • Fetching detailed information about high-value deals from ScaleFluidly for sales analysis or reporting.
  • Integrating deal data into workflows for automated decision-making or notifications.
  • Combining deal insights with other CRM or sales tools within an n8n workflow.

Example: A sales manager could automate the retrieval of high-value deals data daily to update dashboards or trigger alerts when certain thresholds are met.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local (with respective base URLs).
Request JSON object representing the request body sent to the API. This contains parameters specific to the "Get HighValueDealsData" operation.

Output

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

  • The structure of the output JSON depends on the ScaleFluidly API's response for the "Get HighValueDealsData" endpoint.
  • The node does not explicitly handle binary data; all output is JSON-formatted data representing the API response.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers (authorization header).
  • No internal credential names are exposed; users must configure appropriate API credentials or tokens as needed.
  • The node relies on n8n's HTTP request helper methods to communicate with the API.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure that the input data includes valid authorization headers or that credentials are properly configured.
  • Operation not found: If the specified operation (intent) does not match any known endpoint mapping, the node throws an error indicating the operation is invalid. Verify the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause HTTP errors. Check the environment setting and the JSON request body format.
  • Empty or malformed request_info: The request body must be a valid JSON object matching the API expectations for the operation.

Links and References

Discussion