Sparkwise icon

Sparkwise

Execute a Sparkwise model

Overview

This node integrates with Sparkwise models by sending input parameters to a specified Sparkwise model API endpoint and returning the model's response. It is useful for automating predictions or data transformations based on Sparkwise's machine learning models or data processing services.

Typical use cases include:

  • Sending dynamic input data (e.g., location, date) to a Sparkwise model to get predictions or insights.
  • Automating workflows that require invoking Sparkwise models as part of data pipelines.
  • Integrating Sparkwise model outputs into broader automation scenarios in n8n.

For example, you might provide a current location and prediction date to a weather forecasting model hosted on Sparkwise and receive forecast data in return.

Properties

Name Meaning
Model API Endpoint Name or ID Select from a list of available Sparkwise model endpoints or specify an endpoint URL/ID manually. This identifies which Sparkwise model to invoke.
Model Input Values A collection of key-value pairs representing input parameters sent to the Sparkwise model. For example, fields like CurrentLocation or PredictionDate. Multiple fields can be added.

Output

The node outputs an array of JSON objects, each corresponding to the response from the Sparkwise model API for each input item processed.

  • The json output contains the parsed JSON response returned by the Sparkwise model endpoint.
  • No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Sparkwise API.
  • Needs the Sparkwise base URL configured in credentials.
  • Uses HTTP POST requests to communicate with Sparkwise model endpoints.
  • The node dynamically loads available model endpoints from the Sparkwise API to populate the endpoint selection dropdown.

Troubleshooting

  • Invalid Sparkwise URL: If the configured Sparkwise base URL does not start with http:// or https://, the node will throw an error. Ensure the URL is correctly formatted.
  • No endpoint URL selected: The node requires a valid endpoint URL to send requests. Make sure to select or specify one.
  • Invalid endpoint URL: If the endpoint URL is malformed or invalid, an error will be thrown.
  • Authentication failed: If the API key is missing or incorrect, the node will report authentication errors. Verify your API key credential.
  • Resource not found (404): If the requested resource or endpoint does not exist, the node throws a descriptive error indicating the resource was not found.
  • HTTP request failures: Network issues or server errors will cause the node to fail unless "Continue On Fail" is enabled, in which case errors are returned as part of the output array.

Links and References

Discussion