ScaleFluidly icon

ScaleFluidly

Consume ScaleFluidly API

Actions224

Overview

This node integrates with the ScaleFluidly API to perform various operations related to quotes, accounts, contacts, orders, and more within the ScaleFluidly platform. Specifically for the Quote resource and the Create Contact operation, it allows users to create a new contact by sending a JSON request body to the appropriate ScaleFluidly API endpoint.

Common scenarios where this node is beneficial include automating CRM workflows, managing sales contacts programmatically, and integrating ScaleFluidly's quote/contact management capabilities into broader automation pipelines. For example, when a new lead is captured in a marketing system, this node can be used to automatically create a corresponding contact in ScaleFluidly.

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 details of the contact to create. This must conform to the expected API schema for creating a contact.

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 create contact request, typically including details about the newly created contact such as its ID, status, and any metadata returned by the API.

If the API supports or returns binary data (not evident from the provided code), it would be included accordingly, but based on the static analysis, the output is JSON only.

Dependencies

  • Requires access to the ScaleFluidly API endpoints.
  • Needs an API authentication token (bearer token) which should be provided via HTTP headers in the input data or configured through n8n credentials.
  • The node uses the request helper from n8n to make HTTP calls.
  • No explicit external npm packages beyond n8n core dependencies are required.

Troubleshooting

  • Bearer token not found error: If the authorization header with a bearer token is missing in the first input item's JSON headers, the node will throw an error. Ensure that the input data includes valid authorization headers or configure the API credentials properly.
  • Operation not found error: If the specified operation (intent) does not match any known URL mapping, the node will throw an error indicating the operation was not found. Verify that the operation name is correct and supported.
  • Invalid JSON in Request property: Since the request body is user-provided JSON, malformed JSON or missing required fields may cause API errors. Validate the JSON structure before running the node.
  • Environment URL issues: Selecting an incorrect environment or having network connectivity problems to the chosen environment URL will cause request failures.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion