ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API
Join our community

Actions224

Overview

This node integrates with the ScaleFluidly API to execute various operations related to multiple resources, including MCP (presumably a custom or domain-specific resource). Specifically for the MCP resource and the "Execute MCP" operation, the node sends a user-defined intent along with a request body and an access token to the ScaleFluidly API endpoint corresponding to that intent.

Typical use cases include:

  • Executing predefined intents on the ScaleFluidly platform to trigger specific business logic or workflows.
  • Automating interactions with the ScaleFluidly system by sending structured JSON requests.
  • Using different environments (Dev, QA, Local) to test or deploy integrations safely.

For example, a user might want to execute an intent named "create_order" with a detailed JSON payload describing the order, authenticating via a token, and targeting the QA environment.

Properties

Name Meaning
Environment The target environment URL for the API call. Options: Dev (https://documentation-dev.scalefluidly.com), QA (https://documentation.scalefluidly.com), Local (http://localhost:8400).
Intent The name of the user intent to execute on the MCP resource. This determines which API endpoint is called.
Token The access token used for authorization in the API request header. It is required and treated as sensitive information.
Request A JSON object representing the request body sent to the API. This contains the data relevant to the intent being executed.

Output

The node outputs an array of JSON objects, each corresponding to the response from the ScaleFluidly API for each input item processed.

  • The json output field contains the parsed JSON response returned by the API.
  • There is no indication that binary data is handled or returned by this node.

Dependencies

  • Requires an active internet connection to reach the specified ScaleFluidly API environment.
  • Needs a valid access token for authorization; this token must be provided as a string input property.
  • Uses the n8n HTTP request helper methods to perform authenticated API calls.
  • No additional external services or environment variables are explicitly required beyond the access token and environment URL.

Troubleshooting

  • Bearer token not found: If the first input item does not contain an authorization token in its headers and no token was previously set, the node will throw an error. Ensure the access token is correctly provided in the node parameters.
  • Operation not found: If the provided intent name does not map to a known API endpoint, the node throws an error indicating the operation is not found. Verify the intent name matches one of the supported intents defined in the internal intent-to-URL mapping.
  • API request failures: Network issues, invalid tokens, or malformed request bodies can cause HTTP errors. Check the token validity, environment URL correctness, and JSON structure of the request body.
  • Empty or invalid JSON in Request: Since the request body is user-provided JSON, ensure it is well-formed and matches the expected schema for the given intent.

Links and References

(Note: URLs are based on the environment options and may require authentication.)

Discussion