Overview
The Kernex node allows users to interact with the Kernex API, primarily to manage and query resources within a Kernex application. It supports operations such as creating, finding, retrieving, updating, patching, and removing records from specified resources or handling uploads.
A common use case is integrating Kernex data management into automated workflows, for example:
- Automatically fetching filtered lists of resource entries based on dynamic criteria.
- Creating or updating resource records in response to external triggers.
- Removing outdated or irrelevant records programmatically.
This node is beneficial when you want to automate interactions with Kernex without manual API calls, enabling seamless integration with other systems or processes.
Properties
| Name | Meaning |
|---|---|
| Resource Type | Choose between "Resource" (generic Kernex resource) or "Upload" (upload-related endpoint). |
| App ID | The unique identifier of your Kernex application. Required for all operations. |
| Resource Slug | The slug (identifier) of the specific resource within the Kernex app to operate on. Required when Resource Type is "Resource". |
| Operation | The action to perform: Create, Find, Get, Patch, Remove, or Update. |
| ID | The unique ID of the record to get, update, patch, or remove. Required for these operations. |
| Data | JSON object containing data to send when creating, updating, or patching a record. |
| Options | Collection of optional parameters for the Find operation: • Limit: Maximum number of results to return. • Skip: Number of results to skip. • Select Fields: Comma-separated list of fields to return. • Sort: JSON object defining sort order (1 ascending, -1 descending). • Join: JSON array specifying related resources to join. |
| Filters | Collection of filters for the Find operation: • Field Name: Field to filter by. • Filter Type: Type of comparison (Equal, Greater Than, Less Than, Not Equal, Search, etc.). • Value: Value to filter against. |
Output
The node outputs an array of items where each item contains a json property holding the API response data:
- For Find operations, the output is typically an array of resource records matching the query criteria.
- For Get, Create, Update, Patch, and Remove operations, the output is the single resource record or confirmation returned by the API.
- If the response is an array, each element is converted into a separate output item.
- In case of errors (if "Continue On Fail" is enabled), the output includes an item with an
errorfield describing the issue.
The node does not handle binary data output.
Dependencies
- Requires an active Kernex API key credential configured in n8n.
- Network access to
https://api.kernex.io. - Properly set App ID and resource slugs corresponding to your Kernex application.
Troubleshooting
- Invalid Credentials: Ensure the API key credential is valid and has necessary permissions.
- Resource Not Found: Verify that the provided Resource Slug and IDs exist in your Kernex app.
- Malformed Filters or Options: Incorrect JSON syntax in Sort or Join options can cause request failures; validate JSON formatting carefully.
- API Rate Limits or Network Issues: Temporary network problems or rate limiting by Kernex API may cause errors; retry or check API usage limits.
- Missing Required Parameters: Operations like Get, Patch, Update, and Remove require an ID; omitting it will result in errors.
- Error Messages: Errors are returned with their message in the output if "Continue On Fail" is enabled; otherwise, execution stops on first error.
Links and References
- Kernex API Documentation (Assumed official docs for further details)
- n8n Documentation on Creating Custom Nodes