Integration · Databases
AI agents for Appwrite
List databases, tables and columns, find, read, create, update, upsert and delete rows in an Appwrite project's databases (the TablesDB API), and look up the project's users, with a server API key.
- Actions
- 10
- Read
- 6
- Write
- 4
Actions
What your agents can do in Appwrite
List databases, tables and columns, find, read, create, update, upsert and delete rows in an Appwrite project's databases (the TablesDB API), and look up the project's users, with a server API key. Works with Appwrite Cloud in any region and self-hosted Appwrite 1.8 or later.
Read 6
Look things up. Nothing changes.
List databases
Lists the project's databases, optionally only those whose name matches a search term.
List tables
Lists the tables of one database, optionally only those whose name matches a search term.
List columns
Lists the columns of a table: each column's key (the name rows use), type.
Find rows
Lists rows of a table, 25 at a time unless a limit query says otherwise.
Get a row
Reads one row by its ID.
Find users
Lists the project's signed-up users, optionally only those matching a search term (name, email, phone or ID) or queries like {"method":"equal","column":"email","values":["ada@example.com"]}.
Write 4
Create, change or send.
Create a row
Adds a row to a table.
Update a row
Changes some columns of a row by its ID and leaves the others as they are.
Create or replace a row
Writes a row with a known ID: creates it when no row has that ID, or updates it when one does.
Delete a rowDeletes data
Deletes one row by its ID, for good.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Appwrite account.
What you enter
- API key secret
Settings
- API endpoint
- Project ID
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Appwrite data
Ask a question in plain words. The agent can list databases, list tables or list columns in Appwrite, then answers with what it found.
- 02
Let an agent update Appwrite
Have the agent create a row or update a row in Appwrite as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Appwrite and Slack: it can list databases in Appwrite and post a summary to a Slack channel in the same run.
FAQ
Appwrite and MyDeepAgents
Can MyDeepAgents connect to Appwrite?
Yes. The Appwrite connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Appwrite?
Paste an API key from your Appwrite account. You'll need: API key secret. The connection also asks for: API endpoint and Project ID. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Appwrite without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Appwrite in workflows as well as agents?
Yes. Every Appwrite action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Appwrite to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.