Overview
This node allows interaction with the Kernex API to manage resources and uploads within a Kernex application. It supports operations such as creating, finding, retrieving, updating, patching, and removing records from specified resources or handling uploads.
Common scenarios include:
- Managing content or data entries in a Kernex application by creating new records or updating existing ones.
- Querying resources with filters, sorting, and pagination to retrieve specific datasets.
- Deleting records that are no longer needed.
- Handling file uploads related to the Kernex app.
For example, you could use this node to update a product record in an e-commerce Kernex app by specifying the resource slug for products, the record ID, and the updated data fields.
Properties
| Name | Meaning |
|---|---|
| Resource Type | Choose between "Resource" (generic data resource) or "Upload" (file upload endpoint). |
| App ID | The unique identifier of your Kernex application. |
| Resource Slug | The slug (identifier) of the resource you want to interact with (only shown if Resource Type is "Resource"). |
| Operation | The action to perform: Create, Find, Get, Patch, Remove, or Update a record. |
| ID | The 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 record. |
Additional properties for the "Find" operation:
| Name | Meaning |
|---|---|
| Options | Collection of options to control query results: |
| - 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 defining sort order, e.g., {"title":1,"createdAt":-1} (1=ascending, -1=descending). |
| - Join | JSON array defining related resources to join on, e.g., [{"resource":"categories","on":"categoryId","as":"category"}]. |
| Filters | Collection of filters to apply on fields: |
| - Field Name | Name of the field to filter by. |
| - Filter Type | Type of filter: Equal, Not Equal, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal, Search. |
| - Value | Value to filter by. |
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 operations (Get, Create, Update, Patch, Remove), the output
jsoncontains the returned record or confirmation. - For the Find operation, the output can be multiple items, each representing one record matching the query.
- If the node encounters errors and is set to continue on failure, it outputs an item with an
errorproperty describing the issue.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Kernex API.
- Needs network access to
https://api.kernex.io. - No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
- Invalid or missing API key: The node will fail to authenticate. Ensure the API key credential is correctly configured.
- Incorrect App ID or Resource Slug: Requests may return 404 or empty results. Verify these identifiers match your Kernex application setup.
- Invalid JSON in Data or Options: Malformed JSON strings in the Data or Sort/Join fields can cause parsing errors. Use valid JSON syntax.
- Missing required parameters: Operations like Update or Remove require an ID; omitting it will cause errors.
- API rate limits or network issues: May cause request failures; check connectivity and API usage limits.
- When errors occur, enabling "Continue On Fail" allows processing subsequent items without stopping the workflow.
Links and References
- Kernex API Documentation (assumed official docs for further details)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics