ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, configuration, pricing, and administration within the ScaleFluidly platform. Specifically, for the Quote resource and the Update Contact operation, it allows updating contact information associated with a quote by sending a custom JSON request body to the appropriate ScaleFluidly API endpoint.

Common scenarios where this node is beneficial include:

  • Automating updates to contact details linked to sales quotes in ScaleFluidly.
  • Integrating ScaleFluidly quote management into broader workflows, such as CRM or ERP systems.
  • Streamlining quote-related data updates without manual intervention.

For example, a user might update a contact's phone number or email address on a quote automatically when new information is received from another system.

Properties

Name Meaning
Environment The target environment for the API call. Options: Dev (development), QA (quality assurance), Local (local server).
Request The JSON-formatted request body containing the data to update the contact on the quote. This must be provided according to the ScaleFluidly API specification for updating contacts.

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 relevant to the update contact operation.

If the API returns binary data (not typical for this operation), it would be included accordingly, but based on the static analysis, the output is primarily JSON.

Dependencies

  • Requires access to the ScaleFluidly API endpoints specified by the chosen environment URL.
  • Optionally uses an API authentication token if configured; otherwise, it expects a bearer token in the input data headers.
  • No internal credential names are exposed; users must provide valid authorization tokens or credentials configured in n8n.

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. Ensure that either the API key credential is set up in n8n or the input data includes the required authorization header.
  • Operation not found: If the operation name does not map to a known API endpoint, the node throws an error indicating the operation is invalid. Verify the operation parameter matches supported ScaleFluidly operations.
  • Invalid JSON in Request: The Request property must be valid JSON matching the API schema. Malformed JSON or missing required fields may cause API errors.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the specified URL can cause request failures.

Links and References


Note: This summary is based solely on static code analysis of the provided source and property definitions.

Discussion