Overview
This node integrates with the Knack API to manage records within Knack objects. Specifically, the "Record - Create" operation allows users to create new records in a selected Knack object by specifying field values either dynamically based on the object's schema or manually through simple input.
Common scenarios where this node is beneficial include:
- Automating data entry into Knack databases from other systems.
- Creating new customer, order, or inventory records as part of an automated workflow.
- Populating Knack objects with data collected from forms or APIs.
For example, you could use this node to automatically add a new customer record to your Knack CRM whenever a new signup occurs on your website.
Properties
| Name | Meaning |
|---|---|
| Object | Select the Knack object (database table) where the new record will be created. |
| Field Input Mode | Choose how to provide field values: - Dynamic (Schema-based): Fields are generated dynamically based on the object's schema. - Simple (Manual): Manually select fields and enter their values. |
| Fields | When using Simple mode, manually specify one or more fields and their corresponding values to set in the new record. |
| Field Values | When using Dynamic mode, map input data to the object's fields using a resource mapper interface that supports adding all fields and defining mappings below. |
| Additional Options | Optional settings: - Include Field Keys: Whether to duplicate each field value with a "_raw" suffix (e.g., "Name": "John", "Name_raw": "John"). Defaults to true. |
Output
The output JSON contains the newly created record's data with field keys mapped to their display names for readability. If the "Include Field Keys" option is enabled, each field's raw value is also duplicated with a "_raw" suffix.
Example output structure:
{
"id": "record_id",
"Field Display Name 1": "Value 1",
"Field Display Name 1_raw": "Value 1",
"Field Display Name 2": "Value 2",
"Field Display Name 2_raw": "Value 2",
...
}
No binary data is produced by the create operation.
Dependencies
- Requires an API key credential for authenticating with the Knack API.
- The node uses the Knack REST API endpoint (default
https://api.knack.com/v1). - Requires network access to the Knack API.
- The node dynamically fetches object schemas and fields from Knack to support dynamic field mapping.
Troubleshooting
- Missing or invalid credentials: Ensure the API key and application ID are correctly configured in the node credentials.
- Invalid object key: Selecting an object that does not exist or lacks proper permissions will cause errors when fetching fields or creating records.
- Field validation errors: Providing values that do not conform to the field type or required fields missing may result in API errors.
- Network issues: Connectivity problems to the Knack API will cause request failures.
- Incorrect field keys: When using manual mode, ensure field keys correspond exactly to editable fields in the selected object.
If the node throws errors related to HTTP requests or API responses, verify the credentials, object selection, and field inputs.