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 Update Deal Guidances operation, the node sends a request to update deal guidance data within the ScaleFluidly system.

Typical use cases include automating updates to deal guidance information in sales or CRM workflows, ensuring that deal parameters are kept current without manual intervention. For example, a sales automation workflow could trigger this node to update deal guidance details whenever certain conditions are met, such as after a quote revision or approval.

Properties

Name Meaning
Environment The target environment for the API call. Options are:
- Dev (https://documentation-dev.scalefluidly.com)
- QA (https://documentation.scalefluidly.com)
- Local (http://localhost:8400)
Request JSON object representing the request body to be sent with the API call. This contains the data needed to update deal guidances. It must conform to the expected structure required by the ScaleFluidly API for this action.

Output

The node outputs an array of JSON objects corresponding to the responses from the ScaleFluidly API for each input item processed. Each JSON object contains the API response data related to the update of deal guidances.

If the API returns binary data (not indicated explicitly here), it would represent associated files or attachments related to the deal guidance update, but this node primarily handles JSON responses.

Dependencies

  • Requires access to the ScaleFluidly API endpoint specified by the chosen environment.
  • Optionally uses an API authentication token (bearer token) passed via the authorization header in the input data's JSON under headers.authorization.
  • No explicit internal credential names are exposed; users must provide valid authorization tokens as part of the input or configure credentials accordingly.
  • The node depends on n8n's HTTP request helper methods to communicate with the ScaleFluidly API.

Troubleshooting

  • Bearer token not found error: If the first input item does not contain an authorization token in its headers, and no prior token is stored, the node will throw an error. Ensure that the input JSON includes a valid bearer token under json.headers.authorization.
  • Operation not found error: If the operation name does not map to a known intent URL, the node throws an error indicating the operation is invalid. Verify that the operation parameter is correctly set to "update_deal_guidances" for this use case.
  • API request failures: Network issues, incorrect environment URLs, or invalid request bodies can cause API errors. Check the environment setting and ensure the request JSON matches the API specification.
  • Malformed JSON in Request: The request_info property must be valid JSON. Invalid JSON will cause the node to fail.

Links and References


This summary focuses on the Admin resource's Update Deal Guidances operation based on the provided source code and properties.

Discussion