Overview
This node allows interaction with the Kernex API to manage resources and uploads within a Kernex application. It supports operations such as creating, retrieving, updating, patching, finding (searching), and removing records or uploads.
Common scenarios include:
- Fetching a specific resource record by its ID.
- Searching for multiple records with filtering, sorting, and pagination.
- Creating new resource entries or uploading files.
- Updating or patching existing records.
- Deleting records from the Kernex application.
For example, you could use this node to retrieve a user profile by ID, search for all products in a category with sorting, or upload a document to your Kernex app.
Properties
| Name | Meaning |
|---|---|
| Resource Type | Choose between "Resource" (generic data entities) or "Upload" (file uploads). |
| App ID | The unique identifier of your Kernex application. |
| Resource Slug | The slug (identifier) of the resource type you want to interact with (only for Resource type). |
| 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). |
Additional properties for specific operations:
- Data (for Create, Update, Patch): JSON object containing the data to send to the API.
- Options (for Find):
- Limit: Maximum number of results to return.
- Skip: Number of results to skip (for pagination).
- Select Fields: Comma-separated list of fields to return.
- Sort: JSON object specifying sort criteria (e.g.,
{"title":1}for ascending). - Join: JSON array defining related resources to join.
- Filters (for Find):
- Field Name: Field to filter by.
- Filter Type: Type of filter (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 response data from the Kernex API.
- For single record retrieval (
Get), the output is a single JSON object representing the record. - For multiple records (
Find), the output is an array of JSON objects, each representing a record. - For create, update, patch, and remove operations, the output contains the API response confirming the operation result.
- If the node encounters errors and is set to continue on failure, it outputs an object with an
errorfield describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Kernex API.
- The node makes HTTP requests to
https://api.kernex.io/api/v1/{appId}/.... - No additional external dependencies are required beyond standard HTTP access and the provided API key.
Troubleshooting
- Invalid or missing API key: The node will fail if the API key credential is not set or invalid. Ensure the correct API key is configured.
- Incorrect App ID or Resource Slug: Using wrong identifiers will cause API errors or empty responses. Verify these values carefully.
- Missing required parameters: Operations like Get, Patch, Update, and Remove require an ID; omitting it will cause errors.
- Malformed JSON in Data or Options: For fields expecting JSON input (like Data or Sort), ensure valid JSON syntax to avoid parsing errors.
- API rate limits or network issues: Network failures or rate limiting by Kernex API may cause request failures.
- When errors occur, if "Continue On Fail" is enabled, the node outputs error details instead of stopping execution.
Links and References
- Kernex API Documentation (assumed official docs for further details)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics