Kernex icon

Kernex

Interact with Kernex API.

Actions6

Overview

This node integrates with the Kernex API, allowing users to perform various operations on Kernex resources and uploads. It supports creating, retrieving, updating (both patch and full update), finding (searching with filters and options), and removing records within a specified Kernex application.

Common scenarios include:

  • Managing data records in a Kernex application by creating new entries or updating existing ones.
  • Querying resources with complex filters, sorting, and pagination.
  • Uploading files or managing upload-related resources.
  • Deleting records when they are no longer needed.

Practical examples:

  • Patch operation to update specific fields of a resource record identified by its ID.
  • Find operation to retrieve a list of resources filtered by certain criteria and sorted by date.
  • Create operation to add a new resource entry with JSON data.

Properties

Name Meaning
Resource Type Choose between "Resource" or "Upload" to specify the type of Kernex entity to interact with.
App ID The unique identifier of your Kernex application.
Resource Slug The slug (identifier) of the resource within the Kernex app (required if Resource Type is "Resource").
Operation The action to perform: Create, Find, Get, Patch, Remove, or Update.
ID The unique identifier of the record to get, patch, update, or remove.
Data JSON object containing the data to send for create, update, or patch operations.

Additional properties used only for the Find operation:

Name Meaning
Options Collection of parameters 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=asc, -1=desc).
- Join JSON array specifying related resources to join with the main resource.
Filters Collection of filter conditions:
- 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, Patch, Update, Remove), the output contains one item with the JSON response representing the affected record or confirmation.
  • For Find operations, the output may contain multiple items, each representing a resource matching the query.
  • If the API returns an array, each element is converted into a separate output item.
  • No binary data output is handled 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}/....
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Missing or invalid API key will cause authentication errors.
    • Incorrect App ID or Resource Slug will result in 404 or resource not found errors.
    • Invalid JSON in the Data property can cause request failures.
    • Using unsupported filter types or malformed filter values may lead to unexpected results or errors.

  • Error messages:

    • Errors returned from the Kernex API are passed through; typical messages include authorization failures, validation errors, or resource not found.
    • If "Continue On Fail" is enabled, errors are returned as JSON objects with an error property instead of stopping execution.

  • Resolution tips:

    • Verify API key and permissions.
    • Double-check App ID and Resource Slug correctness.
    • Validate JSON syntax in the Data field.
    • Use supported filter types and ensure filter values match expected formats.

Links and References

Discussion