Databases

Knack, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Knack account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Databases
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Knack is

No-code database and business application platform for building custom web apps without coding.

You paste in a key from your own Knack account. It is kept encrypted, and you can withdraw it from inside Knack whenever you like.

How a run works

One message in, the work done in Knack.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Knack. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Knack account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in Knack

These are the ready-made tools your AI employee already has in Knack. It is not limited to them, but it never has to be taught these.

  • 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.
  • 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 b
  • 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 undon
  • 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 undo
  • 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-ba
  • 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
  • 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
  • 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; a
  • 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.
  • 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
Access, and who is in charge of it

You stay the boss of your Knack account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Knack account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Knack is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Knack and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Knack

Can an AI employee really work inside Knack?
Yes. It signs in to your own Knack account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Knack?
No. Nothing moves and nothing is replaced. Your records stay in Knack, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Knack account?
You paste in a key from your own Knack account. It is kept encrypted, and you can withdraw it from inside Knack whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Knack?
It has 10 ready-made tools in Knack today, among them Create object record, Create View Record and Delete Object Record. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Knack and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Knack and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Knack?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Knack is written down with what it did and when.