Knack

Read and write Knack no-code databases from your flows. Agents discover objects and field keys, filter records to drive downstream automation, and create, update, and delete records via the Knack REST API.

7 actions API key available

Knack website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A new order arrives from the storefront with a customer name and email

Get Object reads the customer object's field keys so the agent maps incoming data correctly

List Records filters the customer object on email to find an existing match

Update Record attaches the order to the matched customer, or Create Record adds a new one when nothing matches

The agent compares incoming company name and address against the matched record for conflicts

When the match is ambiguous, same email but a different company name, the operations owner picks which record is right

The day's writes post to the team channel with record links, so the app's owners see what the agent changed

What This Integration Enables

Knack apps have a particular career path: an operations person builds a tracker, the tracker works, and two years later it is the system of record for vendors, members, inventory, or work orders, with the whole company reading from it. What it usually lacks is a connection to the systems where events actually happen. This connector closes that gap. FlowRunner agents read and write Knack records through the REST API, and because Knack identifies tables by object key and fields by keys like field_2, the connector's discovery actions let agents learn the schema at runtime instead of hardcoding it. That matters more than it sounds. The person who built the app keeps evolving it in the Builder. Automations that discover fields before writing survive those changes; automations with hardcoded keys break silently. - Sync records between a Knack app and storefronts, schedulers, and payment systems - Create and update records from form submissions, webhooks, and scheduled runs - Filter records with AND/OR conditions to drive routing and downstream automation - Discover objects and field keys programmatically before composing any payload

Without FlowRunner

The Knack app is an island The database that runs your operation gets updated by hand, from emails and spreadsheets, whenever someone has time

Rekeying is the integration Orders, bookings, and payments happen in other systems, and a person retypes them into Knack hours or days later

Field keys gate every automation Values live under opaque keys like field_12, so every integration attempt starts with someone spelunking the Builder

With FlowRunner

The app joins the workflow Storefront orders, calendar bookings, and payment events write themselves into the right object within minutes

Records stay current without a rekeyer Agents match on unique fields, update what exists, and create only what is genuinely new

Schema discovery is a workflow step Agents call List Objects and Get Object at runtime, so automations adapt when someone adds a field in the Builder

Use Case Scenarios

Orders that file themselves into the operations database

A [Shopify](/integrations/shopify) order fires a trigger. The agent calls List Records against the customer object, filtering on email with the is operator. A match means Update Record appends the order reference and refreshes the contact fields; no match means Create Record adds the customer with values keyed by the field ids Get Object reported. The fulfillment team keeps working from the Knack app they already know, and the app is finally as current as the storefront.

Bookings and payments reconciled into one registry

A [Calendly](/integrations/calendly) booking arrives, and the agent matches the invitee to a member record and stamps the booking date with Update Record. Later, when [Stripe](/integrations/stripe) reports the payment succeeded, a second flow finds the same record and flips its status field to paid, then appends the transaction to a finance log in [Google Sheets](/integrations/google-sheets). Three systems, one member record, and nobody reconciled anything by hand.

The exception report that reads the app for you

On a morning schedule, List Records pulls every work order where the status field is blank or the due date is lower than today. The agent groups the offenders by owner and posts the list to [Slack](/integrations/slack) with record ids and details. The operations lead scans it over coffee and assigns the fixes. The Knack app did not change; what changed is that someone no longer has to remember to go look at it.

Human-in-Loop Highlight

Delete Record is permanent, and in a Knack app that permanence has extra teeth: for many teams the Knack application is the only copy of that operational data. There is no upstream CRM to restore from, because the Knack app is the system of record someone built precisely so the data would live somewhere. So a retention workflow that purges lapsed vendor records never deletes on its own judgment. It filters candidates with List Records, pulls each full record with Get Record, and presents the operations owner with what would be lost: the vendor's history fields, its compliance dates, the records in other objects that reference it. The owner approves the purge list, and only then does Delete Record run. An agent can be trusted to find every record that matches a rule. Deciding the rule was right, on data that exists nowhere else, stays with the person who answers for it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

Schema Discovery

List Objects Lists every object in the Knack application with its key, name, and identifier field. Object keys like object_1 are the stable handles all record operations use, so workflows start here.
Get Object Retrieves one object's full field list: keys, labels, and types. The step that lets agents build correct filters and payloads at runtime instead of hardcoding field_7 and hoping.

Records

List Records Lists an object's records with filtering, sorting, and pagination. Filters are field, operator, value conditions combined with AND or OR, using operators like is, contains, is blank, and higher than. The lookup behind matching, routing, and every exception report.
Get Record Retrieves a single record by id, with values keyed by field id plus HTML-rendered raw values. Used to gather full context before an update, an escalation, or a deletion decision.
Create Record Creates a record from data keyed by field id. Used when matching has confirmed the record is genuinely new, so the app never accumulates duplicates from automation.
Update Record Updates only the fields you provide; everything else keeps its value. The default write for keeping Knack current with events from other systems.
Delete Record Permanently deletes a record by id. Cannot be undone, which is why purge lists on this page carry a human signature before this action fires.

Frequently Asked Questions

What can FlowRunner do with Knack?

FlowRunner agents can run List Objects, Get Object, and List Records in Knack, plus 4 more actions.

Does connecting Knack to FlowRunner require OAuth?

No. Knack connects to FlowRunner with an API key, no OAuth flow required.

Can Knack trigger a FlowRunner workflow automatically?

Knack doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Knack

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us