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, patching, finding (searching), 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 records with filters, sorting, and pagination to retrieve specific datasets.
  • Deleting records when they are no longer needed.
  • Handling file uploads via the "upload" resource type.

Practical examples:

  • Automating the synchronization of customer data from another system into Kernex.
  • Fetching filtered lists of products or categories for reporting or further processing.
  • Removing outdated or incorrect records programmatically.
  • Uploading files related to resources managed in Kernex.

Properties

Name Meaning
Resource Type Choose between "Resource" (data entities) or "Upload" (file uploads).
App ID The unique identifier of your Kernex application where operations will be performed.
Resource Slug The slug (identifier) of the specific resource within the Kernex app (only for Resource type).
Operation The action to perform: Create, Find, Get, Patch, Remove, or Update records.
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 defining sort criteria (e.g., {"title":1} for ascending).
    • Join: JSON array specifying 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, each containing a json field with the response data from the Kernex API.

  • For single-record operations (Get, Create, Update, Patch, Remove), the output contains one item with the JSON representation of the affected record or operation result.
  • For Find operations, the output may contain multiple items, each representing a record matching the query.
  • If the node encounters errors and is set to continue on failure, it outputs an item with a json field containing an error message 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

  • Common issues:

    • Invalid or missing App ID or Resource Slug can cause API errors.
    • Incorrect or expired API key will lead to authentication failures.
    • Providing invalid JSON in Data, Options, or Filters fields may cause request errors.
    • Using an ID that does not exist will result in "not found" errors.

  • Error messages:

    • Errors returned from the Kernex API are passed through in the output under an error property if "Continue On Fail" is enabled.
    • Network or authentication errors typically indicate misconfiguration of credentials or connectivity issues.

  • Resolution tips:

    • Verify all required parameters are correctly filled.
    • Ensure the API key is valid and has necessary permissions.
    • Validate JSON inputs before running the node.
    • Use the Find operation with filters to confirm record existence before attempting Get, Update, Patch, or Remove.

Links and References

Discussion