Automation · Orders and fulfillment

Answer price and stock on WhatsApp and log the order in a Coda table

An AI agent answers price and stock on WhatsApp from the table in your Coda doc and logs the order as a new row for your team.

Show me this with my own operation See every automation

How do I make my WhatsApp answer prices and take orders with the tables I keep in Coda?

A Met connected to Coda, which is now called Superhuman Docs, opens the doc your team uses as a catalog, locates the products table and reads the row for the product the customer asks about: price, stock or delivery time. It answers with that value, not from memory. If the person wants to buy, the Met adds a row to the orders table with the product, the quantity and the details your table asks for, and leaves a comment on that row so someone on the team ships it. If the customer changes something before shipping, the Met updates the same row instead of creating another one.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp to ask how much something costs, whether it is in stock or to place an order. There is no trigger to configure: the Met assigned to the line runs the procedure inside that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Sales Met with catalog and orders in Coda

Sales team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with Coda connected. Its work ends when the customer gets the price and stock the table states and, if they buy, when the order is logged as a row with an alert for the team.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

Coda Automate and collaborate

6 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
Open the catalog doc from its link

The Met's skill carries the link to the doc where the catalog and the orders live. The Met converts it into the ID the other tools use. Superhuman recommends working this way because it is more reliable than searching for the doc by its description.
- url_convert Coda
2
Locate the products table and the orders table

With the doc open, the Met looks up by name the tables your team named, for example "Products" and "Orders". The lookup accepts an approximate name and resolves both in a single call, so it does not write to the wrong table even if the doc has several.
- name_match Coda
3
Read the columns of each table

Before querying or writing, the Met reads the columns: name, type and whether they are writable. That tells it which column to filter the product on, which details to ask the customer for the order and which columns are formulas the doc calculates by itself.
- table_columns_read Coda
4
Bring the product row and answer

The Met reads the products table with a filter on the product the person named and answers with that row's price and stock. Each read brings up to 100 rows; if the customer asks about a whole category, the Met summarizes instead of pasting the table.
- table_rows_read Coda
5
Log the order as a new row

If the person confirms the purchase, the Met adds a row to the orders table with the product, the quantity, the phone number and the details your table asks for, in the writable columns. If the customer changes the quantity or the address before shipping, it updates that same row.
- table_rows_manage Coda
6
Alert the team on the order row

The Met leaves a comment on the new row with a summary of the conversation, so the person who ships sees it in Superhuman Docs without opening WhatsApp. If the product was not in the table, the comment says so and the Met does not make up a price.
- comment_add Coda

Before you start

What you need ready

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

A doc with a products table and an orders table

Your team keeps a Coda doc with one table that has a row per product and clear price and stock columns, and another table for orders. Whatever is not in those tables, the Met does not know.
Coda connected with edit access to that doc

In Met, open Connections → Coda (Superhuman Docs) → Connect and authorize with an account that can edit the doc. According to Superhuman, full usage requires being a Doc Maker on a paid plan; the free plan gives 30 requests per week and a maximum of 60 per month.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that sells. The answer happens inside that conversation; the Coda doc remains the source of data.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not charge or reduce stock on its own. Logging the order does not lower the inventory: if you want it to drop with each order, your doc handles that, and the Met does not write to formula columns.
It does not ask for confirmation in the chat before adding the order row: if the action is on, it adds it. The admin decides in Connections which writes stay on.
It does not log orders in a locked table. If you lock the orders table, the Met cannot add rows unless the lock allows it; lock the products table and leave the orders table open.
It does not fix the catalog. If the row has an old price, the Met answers with that old price; keeping the table up to date is your team's job.

FAQ

Questions about this automation

Lock the products table in the doc: Superhuman does not allow MCP edits on a locked table. Locking is on the Team and Enterprise plans; the orders table stays unlocked so the Met can log orders.

The next answer already uses the new price, because the Met reads the table on every question. There is no copy of the catalog stored in Meteor that goes stale.

To try the procedure, yes. Superhuman counts usage in requests, 30 per week and up to 60 per month, and this procedure calls several tools per order, so for a WhatsApp line with daily traffic a paid plan is the better fit.

Yes. Coda was renamed Superhuman Docs, and your docs and tables stay the same. The connector uses the new MCP server, which according to Superhuman is the one that gets new features.

Keep going