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 Get Field Columns operation, the node sends a request to retrieve metadata about field columns, which can be useful for understanding data structures or customizing UI layouts in ScaleFluidly.

Common scenarios where this node is beneficial include:

  • Fetching metadata about fields to dynamically build forms or interfaces.
  • Retrieving column definitions for admin panels or reporting tools.
  • Automating configuration tasks that depend on field-level details.

For example, an admin user might use this node to get all available field columns for a particular object to customize how data is displayed or validated in their application.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.
Request JSON object representing the request body sent to the API. This contains parameters specific to the operation.

Details on Properties:

  • Environment: Selects the base URL of the ScaleFluidly API environment to interact with (e.g., development, QA, or local).
  • Request: A JSON input that carries the payload for the API call. For "Get Field Columns," this would typically specify filters or identifiers needed by the API to return the relevant field columns.

Output

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

  • The structure of each JSON object depends on the API response for the "Get Field Columns" operation, typically including metadata about fields such as field names, types, labels, and other attributes.
  • The node does not output binary data.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the selected environment.
  • Optionally uses an API key credential configured in n8n for authenticated requests if no explicit authorization header is provided in the input data.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a bearer token, and no credential is configured, the node will throw an error. Ensure that either the input includes a valid authorization header or an API authentication credential is set up in n8n.
  • Operation not found: If the specified operation (intent) does not match any known operation in the internal mapping, the node will error out. Verify the operation name is correct and supported.
  • Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause the node to fail.
  • Network or API errors: Standard HTTP errors from the ScaleFluidly API (e.g., 401 Unauthorized, 404 Not Found) should be checked by reviewing credentials, environment URLs, and request payload correctness.

Links and References


This summary focuses on the Admin resource's Get Field Columns operation based on the provided source code and properties.

Discussion