ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

This node integrates with the ScaleFluidly API, allowing users to perform various administrative and operational tasks related to ScaleFluidly's platform. Specifically, for the Admin resource with the Create Flow operation, it enables creating a new flow within the ScaleFluidly system by sending a custom JSON request body to the appropriate API endpoint.

Common scenarios where this node is beneficial include automating workflow creation in ScaleFluidly environments such as development, QA, or local setups. For example, a user might automate the setup of approval flows or process flows that are part of their sales or operational pipelines.

Practical example:

  • Automatically create a new approval flow when onboarding a new client.
  • Set up customized workflows for different environments (Dev, QA) 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). Determines which ScaleFluidly instance the request will be sent to.
Request The JSON-formatted request body containing the details of the flow to create. This must conform to the expected API schema for creating flows in ScaleFluidly. It is required and should be provided by the user.

Output

The node outputs an array of JSON objects representing the responses from the ScaleFluidly API for each input item processed. Each JSON object corresponds to the API response for the flow creation request, typically including details about the newly created flow such as its ID, status, and any metadata returned by the API.

If the API supports binary data output, it is not explicitly handled here; the output focuses on JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoints corresponding to the selected environment.
  • Optionally uses an API authentication token if provided in the input data headers under authorization.
  • No explicit internal credential type names are exposed; users must configure authentication as per their ScaleFluidly API requirements.
  • The node depends on n8n's HTTP request helper methods to send requests.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization header with a bearer token, and no prior token was stored, the node will throw an error. Ensure that the input JSON includes a valid authorization token in the headers or configure authentication properly.
  • Operation not found error: If the specified operation (intent) does not match any known API endpoint mapping, the node will throw an error indicating the operation is not found. Verify the operation name matches supported ScaleFluidly operations.
  • Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON will cause the API call to fail. Validate JSON syntax before execution.
  • Environment URL issues: Selecting an incorrect or unreachable environment URL will result in network errors. Confirm the environment setting matches your ScaleFluidly deployment.

Links and References

Discussion