Knack icon

Knack

Interact with Knack API

Actions2

Overview

This node integrates with the Knack API to manage records within Knack objects. Specifically, the Record - Get operation retrieves a single record by its ID from a specified Knack object. This is useful when you need to fetch detailed information about a particular entry stored in your Knack database.

Common scenarios:

  • Fetching customer details by their unique record ID.
  • Retrieving a specific order or transaction record for processing.
  • Accessing a single data entry to use in subsequent workflow steps.

Example:
You have a Knack application managing event registrations. Using this node, you can retrieve the registration record of a participant by providing the object (e.g., "Registrations") and the participant's record ID to get all their submitted information.

Properties

Name Meaning
Object The Knack object to operate on. You select which object (table) in your Knack app to query.
Record ID The unique identifier of the record you want to retrieve from the selected object.

Output

The output is a JSON object representing the retrieved record. It includes:

  • id: The record's unique ID.
  • Other fields: Key-value pairs where keys are the field names (mapped from Knack field keys to human-readable labels if available).
  • If enabled, original field keys can be included as additional properties with a _raw suffix.

No binary data is output by this operation.

Example output structure:

{
  "id": "record_id_value",
  "FieldName1": "value1",
  "FieldName2": "value2",
  "FieldName1_raw": "field_1_key"  // optional, if includeFieldKeys option used in search operation (not applicable here)
}

Dependencies

  • Requires an API key credential for authenticating with the Knack API.
  • Needs the Knack Application ID and REST API Key configured in the credentials.
  • Uses the Knack API base URL, defaulting to https://api.knack.com/v1 if not overridden.

Troubleshooting

  • Error fetching record:
    Ensure the provided Record ID exists in the selected object. Invalid or non-existent IDs will cause errors.

  • Authentication errors:
    Verify that the API key and Application ID credentials are correctly set up and have sufficient permissions.

  • Object selection issues:
    If the object list fails to load, check network connectivity and API credentials.

  • Field metadata fetch failure:
    The node attempts to fetch field metadata to map field keys to labels. Failure here won't stop execution but may result in raw field keys in output.

Links and References

Discussion