Overview
This node integrates with the Kernex API, allowing users to perform various operations on Kernex resources and uploads within an n8n workflow. It supports creating, retrieving, updating, patching, finding (searching), and removing records from a specified Kernex application.
Common scenarios include:
- Automating data synchronization between Kernex and other systems.
- Managing resource records programmatically, such as creating new entries or updating existing ones.
- Querying Kernex resources with filters, sorting, and pagination.
- Uploading files to Kernex when using the upload resource type.
For example, you could use this node to automatically create new customer records in Kernex when a form is submitted, or to fetch and process resource data based on specific criteria.
Properties
| Name | Meaning |
|---|---|
| Resource Type | Choose between "Resource" (general Kernex resource) or "Upload" (file uploads). |
| 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 Kernex to operate on (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 those operations). |
| Data | JSON object containing the data to send when creating, updating, or patching a record. |
| Options | Parameters for the Find operation including Limit, Skip, Select Fields, Sort, and Join options. |
| Filters | Filter criteria for the Find operation, specifying field name, filter type (e.g., equal, greater than), and value. |
Output
The node outputs JSON data representing the response from the Kernex API:
- For single record operations (Get, Create, Update, Patch, Remove), the output contains the JSON representation of the affected record.
- For the Find operation, it returns an array of matching records, each as a separate JSON item.
- If the Resource Type is "upload", the node interacts with the uploads endpoint, returning upload-related JSON data.
- 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}/...endpoints. - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly configured and valid.
- Invalid resource slug or app ID: Double-check that the provided App ID and Resource Slug exist and are correct.
- Missing required parameters: Operations like Get, Patch, Update, and Remove require an ID; Create, Update, and Patch require data.
- Malformed JSON in Data or Options: When entering JSON strings (e.g., for sort or join), ensure proper JSON syntax to avoid parsing errors.
- API rate limits or network issues: Handle possible request failures by enabling "Continue On Fail" in the node settings to prevent workflow interruption.
Links and References
- Kernex API Documentation (Assumed official docs URL)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics.