Automation · Orders and fulfillment

Check on WhatsApp how a customer's order stored in your Supabase database is going

Your team asks on WhatsApp how an order is going: an AI agent queries the orders table in Supabase and leaves the note in the CRM.

Show me this with my own operation See every automation

How do I check how an order stored in Supabase is going without opening the dashboard?

Someone on your team writes to the internal Met "how is Laura Gómez's order going?". The Met finds Laura in Meteor's CRM to get her phone number, locates your Supabase project, checks the tables to find the orders one and, if the admin turned on the SQL query, which starts turned off, runs a read query by that phone number. It replies with the order's status, date and number, and leaves an internal note on Laura's contact with what it found, so the rep serving her can answer. The Met does not talk to the customer: Supabase recommends not giving its MCP server to customers.

What starts it

When someone asks for it

It starts when someone on the team asks the Met on WhatsApp about a customer's order. Each query runs on request, and the Met replies inside that same conversation with the team.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Internal Met that queries your orders database in Supabase

This is not a named, seeded Met. It is an internal Met with Supabase and the CRM connected, which only serves the team: its work ends when it replies with the order status and leaves the note on the customer's contact, or when it says it did not find the order.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

Supabase Automate and collaborate
Meteor CRM Sell and serve

5 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Find the customer in the CRM

The Met searches Meteor's CRM by name for the contact it is asked about and takes their phone number, which is the field used to look up orders in your database.
- crm_search_contacts Meteor CRM
2
Locate the Supabase project

The Met lists the projects of the connected account and brings the details of the one that stores the orders, the one you set in its instructions.
- list_projects Supabase
- get_project Supabase
3
Find the orders table

The Met lists the database tables and finds the orders one, so it writes the query on the real table and not on the one it assumes.
- list_tables Supabase
4
Query the order

The SQL query starts turned off: the admin turns it on in Connections for this step. The Met runs a read query, a SELECT by the customer's phone number, and takes the most recent order with its status, date and number.
- execute_sql Supabase
5
Reply and leave the note

The Met replies to whoever asked and leaves an internal note on the customer's contact in the CRM with the order status. That note is the only write in this procedure.
- crm_add_note Meteor CRM

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

Supabase connected in Met

In Met, open Connections → Supabase → Connect, sign in and choose the organization that contains the orders project.
An internal Met, not the one that serves customers

Assign the connector to a Met that only serves your team on WhatsApp. Supabase recommends not giving it to customers, and Met's connection is not in read-only mode.
Instructions that keep SQL to reading

Write in the Met's instructions the project, the orders table and that it should only run SELECT queries. The admin turns on only the SQL query, which starts turned off, and leaves the migration, Edge Function, project and branch actions off.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not stop the query from writing. Once turned on, execute_sql runs the SQL the Met writes and the connection is not read-only; what keeps it to SELECT is its instructions, not the tool.
It does not answer the customer. Supabase recommends not giving its MCP server to customers, so the Met replies to the team and the rep gives the customer the answer.
It does not find orders stored under another field. If your table does not have the customer's phone number, it has to search by another field, and that goes in the Met's instructions.
It does not change the order status. The procedure only reads the Supabase database; the only write is the note in Meteor's CRM.

FAQ

Questions about this automation

Because Supabase recommends not giving its MCP server to customers or end users: it runs with developer permissions, and a message with hidden instructions could lead the Met to query something else.

Yes, any table the connected account can see. It helps to write in the instructions which tables it may query, so it does not read more than needed.

Not for this procedure. Supabase keeps development branches for paid plans, and this procedure does not use them.

Keep going