ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions98

Overview

The "Update Flow" operation within the Admin resource of the ScaleFluidly node allows users to interact with the ScaleFluidly API to update workflow or flow-related data in the ScaleFluidly system. This node is designed to send HTTP requests to different environments (Dev, QA, Local) of the ScaleFluidly API, using a bearer token for authorization.

Typical use cases include automating updates to flows or workflows managed by ScaleFluidly, integrating flow updates into larger automation pipelines, or synchronizing flow data between systems. For example, a user might update a sales process flow or approval workflow dynamically based on external triggers or data changes.

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 the base URL for the API request.
Request JSON object representing the request body sent to the API. Contains the data needed to update the flow. This is required and must be provided as valid JSON.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each output JSON object contains the response data returned by the API after attempting to update the flow.

If the API returns binary data (not indicated explicitly in this code), it would be included accordingly, but based on the static analysis, the output is primarily JSON data reflecting the API response.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Needs a valid bearer token for authorization, which must be provided in the input data's headers or via authentication configured in n8n.
  • The node optionally uses an API credential configured in n8n for authenticated requests if no explicit bearer token is found.
  • No other external dependencies are indicated.

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 "Bearer token not found". Ensure that the authorization token is correctly set either in the input data headers or via n8n credentials.
  • Operation not found: If the specified operation (intent) does not match any known endpoint mapping, the node throws an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • Invalid JSON in Request: The request_info property must be valid JSON. Malformed JSON will cause errors when sending the request.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity issues to the chosen environment URL can cause request failures.

Links and References

Discussion