Kernex

Interact with Kernex API.

Actions6

Overview

This node allows interaction with the Kernex API to manage resources and uploads within a Kernex application. It supports creating, retrieving, updating, patching, finding, and removing records or uploads by making HTTP requests to the Kernex API endpoints.

Common scenarios include:

Creating new resource entries in a Kernex app.
Uploading files or data to Kernex.
Querying existing resources with filters, sorting, and pagination.
Updating or patching existing resource records.
Deleting resource records.

Practical example: You can use this node to automate adding new customer records to your Kernex database or to upload documents related to those customers, then later query or update those records as needed.

Properties

Name	Meaning
Resource Type	Choose between "Resource" (generic data resource) or "Upload" (file/data upload endpoint).
App ID	The unique identifier of your Kernex application where the operations will be performed.
Resource Slug	The slug (identifier) of the specific resource within the Kernex app (required if Resource).
Operation	The action to perform: Create, Find, Get, Patch, Remove, or Update on the selected resource.
ID	The unique ID of the record to get, patch, update, or remove (required for these operations).
Data	JSON object containing the data to send when creating, updating, or patching a resource.

Output

The node outputs an array of items, each containing a json field with the response from the Kernex API:

For Create, Update, Patch, Get, and Remove operations, the output is the JSON representation of the affected resource or confirmation of deletion.
For Find operations, the output is an array of matching resource objects based on the query parameters.
If multiple results are returned (e.g., from a find operation), each result is output as a separate item.
No binary data output is produced by this node.

Dependencies

Requires an API key credential for authenticating with the Kernex API.
Needs network access to https://api.kernex.io.
The user must provide the Kernex Application ID and appropriate resource slugs or IDs.
No additional external libraries beyond standard HTTP request helpers provided by n8n.

Troubleshooting

Invalid API Key or Authentication Errors: Ensure the API key credential is correctly configured and has permissions for the Kernex app.
Missing Required Parameters: Operations like create, update, patch, and remove require specific fields such as appId, resourceSlug (for resources), id (for certain operations), and data (for create/update/patch). Missing these will cause errors.
Malformed JSON in Data Field: The data property expects valid JSON; invalid JSON will cause request failures.
Network Issues: Connectivity problems to the Kernex API endpoint will result in request timeouts or errors.
API Limitations: The find operation supports filtering, sorting, limiting, and skipping results. Incorrect filter syntax or unsupported queries may return empty results or errors.
When errors occur, if the node is set to continue on fail, error messages are returned in the output JSON under an error field.

Links and References

Kernex API Documentation (Assumed official docs for further details)
n8n HTTP Request Node documentation for understanding request options and error handling.