Search and data
Knack for AI agents.
Managed auth, ready-made tools.
List, read, create, update and delete records in Knack apps on behalf of each of your users.
About Knack
With the Knack connector, your agent works with records in each user’s own Knack apps. It can list and filter records in an object, read a record, add a new one, update it or delete it, using only the tools your project allows.
Knack is a no-code platform for building online databases and business apps.
Tools
What your agent can do in Knack.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Knack connection.
-
List records
Readknack_list_recordsList and filter the records of an object.
-
Get a record
Readknack_get_recordRead one record.
-
Create a record
Writeknack_create_recordAdd a new record to an object.
-
Update a record
Writeknack_update_recordChange the fields of a record.
-
Delete a record
Writeknack_delete_recordDelete a record.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Knack, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read and add records, and switch off
knack_delete_recordso it can never delete one. -
Restrict what the agent reaches
Choose the endpoints a project may use, for example reading records but not writing them. A call outside them is refused.
Get started
Connect Knack
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Knack
Each end user authorizes their own Knack account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Knack account, once. const connection = await agent200 .user("user_123") .connect("knack"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Knack tools
Name the user, the model and the tools. The model decides which Knack tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "List the open orders in my Knack app", tools: ["knack"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, connecting their own Knack app. Each connection belongs to that user.
-
What access is requested
Access to the records of the app they connect. Users can revoke it later from their Knack account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Knack connector and how to use it.
Connector: Knack, through Agent200. In code: "knack". What it does: List, read, create, update and delete records in Knack apps on behalf of each of your users. Page: https://www.agent200.com/connectors/knack/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Knack's own page, through the authorization link Agent200 returns. Never ask a user for a Knack password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: knack_list_records, knack_get_record. Write tools: knack_create_record, knack_update_record, knack_delete_record. Name "knack" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/knack/framework/claude/ https://www.agent200.com/connectors/knack/framework/chatgpt/ https://www.agent200.com/connectors/knack/framework/claude-code/ https://www.agent200.com/connectors/knack/framework/muse/ https://www.agent200.com/connectors/knack/framework/grok-bot/ https://www.agent200.com/connectors/knack/framework/openai-dots/ https://www.agent200.com/connectors/knack/framework/claude-duet/ https://www.agent200.com/connectors/knack/framework/hermes-agent/ https://www.agent200.com/connectors/knack/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/knack.md
Guides
Use Knack with the AI you build on.
Step-by-step setup for Knack with a specific model, assistant or agent framework.
-
Knack + Claude
How to connect Knack to Claude
-
Knack + ChatGPT
How to connect Knack to ChatGPT
-
Knack + Claude Code
How to connect Knack to Claude Code
-
Knack + Muse
How to connect Knack to Muse
-
Knack + Grok Bot
How to connect Knack to Grok Bot
-
Knack + OpenAI Dots
How to connect Knack to OpenAI Dots
-
Knack + Claude Duet
How to connect Knack to Claude Duet
-
Knack + Hermes Agent
How to connect Knack to Hermes Agent
-
Knack + OpenClaw
How to connect Knack to OpenClaw
FAQ
Knack and Agent200, answered.
Who handles the Knack OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Knack.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Knack connection, never another user's. It cannot reach anything the user or Knack has not authorized.
Can I limit what my agent can do in Knack?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.