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 with the Get Locations operation, it fetches location-related data from the ScaleFluidly system.

Typical use cases include:

  • Retrieving administrative location data for internal dashboards or workflows.
  • Automating the synchronization of location information between ScaleFluidly and other systems.
  • Using location data to drive decision-making or trigger further automation steps in n8n.

For example, a user might configure this node to pull all available office or warehouse locations from ScaleFluidly to update a CRM or ERP system automatically.

Properties

Name Meaning
Environment The target environment URL for the ScaleFluidly API. Options: Dev, QA, Local.
  • Environment selects which ScaleFluidly API endpoint to interact with:
    • Dev: Development environment URL.
    • QA: Quality Assurance environment URL.
    • Local: Localhost URL for local testing.

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 specific API response for the "Get Locations" operation but generally includes location details such as IDs, names, addresses, or other metadata.
  • No binary data output is produced by this node.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the selected environment.
  • Optionally uses an API authentication token (Bearer token) passed via input data headers or credentials configured in n8n.
  • No explicit external npm packages beyond standard n8n workflow helpers are required.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization header with a Bearer token, and no token is stored in static workflow data, the node will throw an error. Ensure that the token is provided either in the input data headers or configured properly.
  • Operation not found: If the specified operation does not exist in the intent-to-URL mapping, the node throws an error indicating the operation is invalid. Verify the operation name matches supported actions.
  • API request failures: Network issues, incorrect environment URLs, or invalid tokens can cause request errors. Check connectivity, environment selection, and token validity.
  • Invalid JSON in Request Body: For operations requiring a request body, ensure the JSON is well-formed.

Links and References

Discussion