ScaleFluidlyInstall

Overview

This node integrates with the ScaleFluidly API, allowing users to perform a wide range of operations across different resources such as quotes, configuration, pricing, admin, and MCP (a custom module). Specifically, for the Configure resource and the UniversalSearch Objects operation, it enables searching objects universally within the ScaleFluidly platform.

Typical use cases include:

• Searching various object types in a unified manner without needing separate queries per object type.
• Automating retrieval of configuration-related data for further processing or decision-making.
• Integrating ScaleFluidly's search capabilities into workflows to dynamically fetch relevant configuration objects based on criteria.

For example, a user might want to search all configuration objects matching certain filters to update or analyze them automatically.

Properties

• Environment options:

  • Dev: Development environment URL
  • QA: Quality Assurance environment URL
  • Local: Localhost URL for local testing

• Request: This is a JSON input where you specify the search parameters according to the ScaleFluidly API's expected format for the universal search operation.

Output

The node outputs an array of JSON objects representing the results returned by the ScaleFluidly API for the universal search query. Each item corresponds to an object found by the search, structured as per the API response.

If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is JSON data reflecting the searched objects.

Dependencies

• Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
• Optionally uses an API authentication token if provided in the input data headers; otherwise, it attempts to use stored credentials configured in n8n under a generic API key credential.
• No other external dependencies are required.

Troubleshooting

• Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no stored credentials are available, the node will throw an error. Ensure that either the input includes a valid authorization token or proper API credentials are configured in n8n.
• Operation not found: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify the operation name matches one of the supported operations.
• Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause the request to fail.
• API connectivity issues: Check network connectivity and correct environment URL selection if requests time out or fail.

Links and References

• ScaleFluidly API Documentation (QA environment)
• ScaleFluidly Developer Portal (if available)
• n8n documentation on HTTP Request Node for understanding how API calls are made internally.

This summary focuses on the Configure resource's UniversalSearch Objects operation, describing its inputs, outputs, and usage context based on static code analysis.