No-code database and business application platform for building custom web apps without coding.
No-code database and business application platform for building custom web apps without coding. On Nagent, Knack is exposed as a fully-configurable databases integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Knack into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Knack to automate the kinds of tasks databases teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Knack into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Knack, with input parameters and output schema. Drop these into any step of an agent built in Helix.
KNACK_CREATE_OBJECT_RECORDTool to create a new record in a specific Knack object. Use when you need to add new data to a Knack database object. Requires object-based API key authentication.
Input parameters
Dictionary of field keys and their values. Keys must match your Knack object's field keys (e.g., 'field_1', 'field_2'). Values can be strings, numbers, objects, or arrays depending on the field type. For name fields, use {'first': 'John', 'last': 'Doe'}. For email fields, use {'email': 'user@example.com'}.
The object key identifier (e.g., 'object_1', 'object_2'). This identifies which Knack object to create the record in.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_CREATE_VIEW_RECORDTool to create a new record through a form view in Knack. Use when you need to add a record to a Knack object using a form view interface. Only fields that exist in the form will be used, and any record rules configured on the form will be triggered.
Input parameters
The view key for the form view through which to create the record (e.g., 'view_12').
The scene/page key where the form view is located (e.g., 'scene_13').
JSON object containing field keys and their values. Field keys must match the fields defined in the form view (e.g., {'field_1': {'first': 'John', 'last': 'Doe'}, 'field_2': 'john@example.com'}). Only fields that exist in the form will be used.
User token for login-protected pages. Only required if the form view requires authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_DELETE_OBJECT_RECORDTool to delete a single record from a specific Knack object by its ID. Use when you need to permanently remove a record from an object. This action is permanent and cannot be undone. Requires API key authentication (X-Knack-Application-Id and X-Knack-REST-API-KEY headers).
Input parameters
The unique ID of the record to delete. This operation is permanent and cannot be undone.
The object key (e.g., object_1, object_2). This identifies which object the record belongs to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_DELETE_VIEW_RECORDTool to delete a record through a view that contains a delete link. Works with tables, lists, searches, calendars, and details views. This operation is permanent and cannot be undone. Use only after confirming the correct scene_key, view_key, and record_id.
Input parameters
The view key for a view with delete link (e.g., view_2). Must be a view that contains delete functionality.
The record ID to delete. This operation is permanent and cannot be undone.
The scene/page key (e.g., scene_10). Identifies the page containing the view.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_GET_OBJECT_RECORDTool to retrieve a single record by its ID from a specific Knack object. Returns the complete record with all field values in both formatted and raw formats. Use this for object-based access which requires API key authentication.
Input parameters
The unique record ID to retrieve (e.g., '58643557d1ea9432222f3cbb'). This is a 24-character hexadecimal string.
The object key identifier (e.g., 'object_1', 'object_2'). This can be found in your Knack application's API settings or builder interface.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_LIST_OBJECT_RECORDSTool to retrieve multiple records from a specific Knack object (table). Returns up to 1000 records per page with pagination support. Use this for object-based access which requires API key authentication and provides full access to all fields and records. Supports filtering by field values and sorting by field keys.
Input parameters
Page number for pagination (default 1). Use this to navigate through multiple pages of results.
URL-encoded JSON filter object. Must contain 'match' (and/or) and 'rules' array. Example: {"match":"and","rules":\[{"field":"field_1","operator":"is","value":"test"}\]}
The object key identifier (e.g., object_1, object_2). This identifies which Knack object (table) to retrieve records from.
Field key to sort results by (e.g., field_25). Must be a valid field key from the object.
Sort order enumeration for records.
Number of records per page (default 25, max 1000). Controls how many records are returned in a single request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_LIST_VIEW_RECORDSTool to retrieve multiple records from a specific Knack view (tables, lists, searches, calendars). Use when you need to fetch data from a view with pagination support. Returns only fields included in the view configuration.
Input parameters
Page number for pagination. Defaults to 1 if not specified.
The view key (e.g., view_1, view_11). This identifies the specific view (table, list, search, or calendar) to retrieve records from.
The scene/page key (e.g., scene_1). This identifies the page containing the view.
Number of records per page. Maximum is 1000. Defaults to 25 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_UPDATE_OBJECT_RECORDTool to update an existing record in a specific Knack object. Use when you need to modify field values in an existing record. Only fields provided in the request will be updated; all other fields remain unchanged.
Input parameters
Dictionary of field keys and their values to update. Only fields included in this dictionary will be modified; all other fields remain unchanged. Keys must match your Knack object's field keys (e.g., 'field_1', 'field_4'). Values can be strings, numbers, objects, or arrays depending on the field type.
The unique record ID to update (e.g., '67e1e50c2fa13b511d7770aa'). This is a 24-character hexadecimal string.
The object key identifier (e.g., 'object_1', 'object_2'). This identifies which Knack object contains the record to update.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_UPLOAD_FILETool to upload a file to a Knack application. This is step 1 of a two-step process - after uploading, use the returned file ID when creating or updating a record with a file field.
Input parameters
The file to upload to Knack.
Your Knack application ID. This identifies which application to upload the file to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KNACK_UPLOAD_IMAGETool to upload an image to a Knack application. This is the first step in a two-step process - after uploading, use the returned file ID when creating or updating a record with an image field. Use when you need to attach images to Knack records.
Input parameters
The image file to upload.
Your Knack application ID. This identifies which application to upload the image to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 50 agents privately built on Nagent that already use Knack.
Build on Nagent
Connect Knack to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Knack, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Knack is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Knack is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Knack steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Knack event fires, the agent kicks off automatically.
Every Knack action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Knack ships with 10 pre-built databases actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Knack together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Knack-based workflows tailored to your business.