Support lookup
Support asks why the Acme account cannot log in. Memtro finds the user by email in Appwrite and shows their status, labels and whether the email is verified, then reads their latest rows in the sessions table.
Appwrite + Memtro
Ask Appwrite for rows in any table, users and storage files.
Connect Appwrite with your project ID and an API key and Memtro reads your project's own data: tables, rows, users, files, messages and functions. A server key bypasses row permissions, so give Memtro its own narrow key. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create, change or permanently delete rows and files, send email, SMS and push messages that reach people outside the company, create, block or delete users, manage teams, and run functions, whose compute may be billed.
In Memtro
What you can do with Appwrite in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Appwrite tool, reads what it needs, and answers with the source cited.
What it does
- 01Databases in the project, tables in each, and each table's columns with type and default
- 02Rows of a table with filters such as status equal to open, ordering and offset, and one row by id
- 03Users with name, email, status, labels and when they registered, and team members
- 04Storage buckets and files, messaging topics and messages, and the project's functions
- 05When asked and granted, creates, changes or increments rows, running your Functions and webhooks, permanently deletes a row or file, or runs a function, which may be billed
- 06When asked and granted, sends email, SMS or push through Appwrite Messaging to people outside the company, and creates, blocks, relabels or permanently deletes users and manages teams
Acts when asked
When you ask it to
These tools change something in Appwrite. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Create a row in an Appwrite table
- 02Change fields of an Appwrite row
- 03Create or replace an Appwrite row by id
- 04Delete an Appwrite row
- 05Delete a file from Appwrite storage
- 06Send an email through Appwrite Messaging
- 07Send an SMS through Appwrite Messaging
- 08Send a push notification through Appwrite Messaging
- 09Delete an Appwrite message (does not recall a sent one)
- 10Create an Appwrite messaging topic
- 11Create an Appwrite user
- 12Block or unblock an Appwrite user
- 13Rename an Appwrite user
- 14Set an Appwrite user's labels
- 15Delete an Appwrite user
- 16Run an Appwrite function
- 17Create an Appwrite team
- 18Add a member to an Appwrite team
- 19Remove a member from an Appwrite team
- 20Increment a number column of an Appwrite row
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Appwrite for you. Each event can start a job, with the event as its input. Appwrite signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01A user was created
- 02A user was deleted
- 03A user was blocked or unblocked
- 04A user's email address changed
- 05A user's name changed
- 06A team was created
- 07A team was deleted
- 08A team membership was created
- 09A team membership was deleted
- 10A row was created
- 11A row was updated
- 12A row was upserted
- 13A row was deleted
- 14A file was uploaded (fires per 5MB chunk)
- 15A file was deleted
- 16A function execution was created
- 17A function execution was updated
- 18A function deployment was created
- 19A message was created
- 20A message was updated
- 21A topic subscriber was created
In practice
Ask it like you would a colleague
Once Appwrite is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Appwrite + Memtro
How many orders are still open in the shop database?
Which users signed up this week?
What columns does the tickets table have?
Set the status of order row a91f to shipped
Send a push to the beta-testers topic that version 2.3 is out
Telling the testers
Dan Fletcher asks Memtro to tell the Northwind beta testers that version 2.3 is ready. Memtro sends his approved words as a push notification to the beta-testers topic through Appwrite Messaging, and every subscribed device is notified.
Teams
Where it fits
The teams that lean on Appwrite most, a question each of them asks, and what they connect beside it.
- Data and analyticsQuestions answered from the warehouse, with the SQL shownAnalyst, Data engineer, Anybody with a question, Head of data“Revenue by segment for Q3 from the warehouse, with the SQL you used”Used alongside Postgres, Stripe, Slack, Google Drive, Snowflake and 3 more.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- FinanceAsk the ledger questions in plain EnglishFinance lead, Credit control, Management accountant, Founder or CFO“Which invoices over £5k are more than 30 days overdue?”Used alongside Xero, Stripe, Postgres, HubSpot, QuickBooks Online and 10 more.
Better together
Works with
A record in Appwrite is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- AnalyticsAppwrite with Google Analytics 4Ask your traffic questions in plain English and get the numbers back.
- AnalyticsAppwrite with Plausible AnalyticsAsk about your website traffic in plain English.
- AnalyticsAppwrite with UmamiAsk about your website traffic in plain English, without sending anybody to a dashboard.
- Finance and commerceAppwrite with XeroInvoices, bills, contacts and reports, answered in plain English with figures cited to Xero.
- Finance and commerceAppwrite with StripeCustomers, charges, invoices and subscriptions through a restricted key.
- Finance and commerceAppwrite with FellohBookings, payments, refunds, chargebacks, supplier payments and payouts from the travel payments platform.
- Work managementAppwrite with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementAppwrite with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementAppwrite with LinearIssues, projects and teams, synced hourly into memory.
Also in Databases and warehouses
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- Postgres
- MySQL and MariaDB
- SQL Server
- BigQuery
- Snowflake
- AWS Athena
- MongoDB
- ClickHouse
- Amazon Redshift
- Databricks
- Elasticsearch
- dbt Cloud
- Fivetran
- Neon
Grist- Hasura
- Meilisearch
NocoDB- Qdrant
Typesense
Weaviate
Tinybird
Hightouch
Census- Airbyte
- Budibase
- CockroachDB Cloud
- Cube Cloud
- DataHub
kintone
Monte Carlo
OpenMetadata- Pinecone
- PlanetScale
- Quickbase
Secoda
Softr
Teable- Turso
- Upstash
Vectara- Xata
- Zilliz Cloud
Setup
How to connect
Connect withProject ID and API key
- 1
Needs Appwrite 1.8 or later. Copy the Project ID from Appwrite Console → your project → Settings
- 2
In Console → your project → API Keys → Create API key, give read scopes for databases, tables, rows, users, buckets and files, and the matching write scopes such as rows.write, messages.write, users.write or executions.write only if Memtro may act on them
- 3
In Connections → Appwrite in Memtro paste the Project ID and API key, and leave Host blank for cloud.appwrite.io, or type your region's host or self-hosted server's public host name only
- 4
Ask how many rows in the orders table are still open
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Appwrite tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Appwrite?+
Only when you ask, and only what it has been granted: create a row in an Appwrite table; change fields of an Appwrite row; create or replace an Appwrite row by id; delete an Appwrite row; delete a file from Appwrite storage; send an email through Appwrite Messaging; send an SMS through Appwrite Messaging; send a push notification through Appwrite Messaging; delete an Appwrite message (does not recall a sent one); create an Appwrite messaging topic; create an Appwrite user; block or unblock an Appwrite user; rename an Appwrite user; set an Appwrite user's labels; delete an Appwrite user; run an Appwrite function; create an Appwrite team; add a member to an Appwrite team; remove a member from an Appwrite team; increment a number column of an Appwrite row. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a Appwrite connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Appwrite data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect Appwrite?+
Project ID and API key. Needs Appwrite 1.8 or later. Copy the Project ID from Appwrite Console → your project → Settings.
Can Appwrite start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Appwrite for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect Appwrite in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.