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, and MCP. Specifically for the Admin resource and the Request Free Trial operation, the node sends a custom JSON request body to the ScaleFluidly API endpoint designated for requesting a free trial.

Typical use cases include automating administrative tasks related to ScaleFluidly, such as initiating free trial requests programmatically within workflows. For example, a user could trigger this node when a new lead is captured, automatically sending a free trial request to ScaleFluidly without manual intervention.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400). This determines which ScaleFluidly instance the request will be sent to.
Request A JSON object representing the request body to send with the API call. This must be provided and contains the details required by the "Request Free Trial" operation on the Admin resource.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each output JSON object contains the parsed response data returned by the API after performing the requested operation.

If the API returns binary data (not indicated in this case), it would be included accordingly, but for the "Request Free Trial" operation, the output is expected to be JSON-formatted response data.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Optionally uses an API authentication token if provided in the input data headers or via configured credentials.
  • No explicit internal credential names are exposed; users must provide appropriate API authentication tokens or credentials as per their ScaleFluidly setup.
  • The node supports three environments (Dev, QA, Local) selectable via the Environment property.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token and no other authorization method is configured, the node will throw an error. Ensure that the input data includes a valid bearer token in the headers or that the node is properly configured with API credentials.
  • Operation not found error: If the specified operation (intent) does not match any known operation URL mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause API request errors. Check the environment URL, ensure the request JSON is correctly formatted, and verify API availability.
  • Empty or malformed request body: Since the request body is required, providing an empty or invalid JSON object may result in API errors. Validate the JSON structure before execution.

Links and References

Discussion